Common Issues When Using IpaGuard

Will obfuscation affect performance?

Solution: Obfuscation does not affect performance and does not change the code logic.

---

What if the processed IPA cannot run?

Solution: Crashes or failure to run may occur if non-obfuscatable content was included. Reduce the obfuscation scope, including system functions.

---

How to test the obfuscated IPA

Solution: Configure signing information in IpaGuard; the tool will automatically sign the IPA after obfuscation. Development certificates can install on test devices; distribution certificates can be used for submission.

---

What does different obfuscation strength mean?

Solution: Different strengths indicate the readability of functions and file names after obfuscation; higher strength = less readable.

---

AppleMobileDeviceService.exe not installed

Possible error:

1dial tcp 127.0.0.1:27015: connectex: No connection could be made because the target machine actively refused it

Solution: Install iTunes and check USB connection or if AppleMobileDeviceService.exe is running in Task Manager.

---

developerDiskImageFiles not downloaded

When first processing or signing for testing, missing developerDiskImageFiles may cause:

1Mounter Developer Image file Failed: Get "https://github.com/mspvirajpatel/Xcode_Developer_Disk_Images/blob/master/Developer%20Disk%20Image/16.5/DeveloperDiskImage.dmg?raw=true": read tcp 192.168.1.254:56262->20.205.243.166:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. May be downloading the required file,please check the network and try later

Solution:The program will automatically download developerDiskImageFiles to IpaGuard\developerDiskImageFiles. Wait for the download before retrying.

---

No Apple device connected via USB or network

Possible error:

1未检测到可安装测试设备: no installable devices` 

Solution: Connect the device via USB (recommended) or network. Trust the device when prompted. Enable the “Install to Device” option in re-sign module. The IPA can then be installed directly on the device.

---

How to Set App Normal Launch Time

Solution: This indicates the time required for the app to start normally on the device. It is mainly used to detect potential crashes or issues during automatic obfuscation. This setting does not affect the use of the “Start Processing” button. For beginners, it is recommended to configure and then click “Start Processing” directly; experienced users can click “Start Auto Obfuscation” (also called the auto-obfuscation button). Note that either button must be clicked only after configuration is complete.

---

Warnings During IPA Processing

Solution: Warnings can be ignored.

---

App Crashes After IPA Obfuscation

Solution: Dynamically called methods may not be obfuscated correctly. It is recommended to obfuscate only part of the code instead of all. Test installation after obfuscation is advised.

---

How to Obfuscate uniapp Packages

Solution: IpaGuard supports IPA from any development platform. Be cautious with dynamic reflection code, which may cause crashes. Choose obfuscation targets based on actual requirements.

---

Device Locked (InvalidService)

Solution: Device lock prevents installation. Unlock the device before proceeding.

---

Error: DVTSecureSocketProxy with reason: “Invalid process Failed”

Solution: iOS version may be too high (e.g., 17.0.2). Ensure the device iOS version is supported (currently up to iOS 16).

---

Re-sign Error 90035

Solution: Use a distribution certificate and select “Yes” for re-sign. If the error persists, check the certificate type or use Mac codesign to inspect the IPA.

---

Log Shows 0 Files Processed

Solution: __objc_classname warning indicates no OC class data in the executable. Check the OC class module.

---

Will Files Be Obfuscated If Not Manually Selected?

Solution: Default is not to process.

---

Will Unique UDID of Each OC Class File Be Lost After Obfuscation?

Solution: Automatically preserved/modified.

---

Does Obfuscation Add Junk Code?

Solution: Not yet. Can verify using Mac native signing.

---

Rejected 2.3.1

Solution: Feature hidden; contact Apple support.

---

Distribution AdHoc vs Release Signing

Solution: Depends on account type. Enterprise accounts support AdHoc. Check signature via Mac codesign before upload.

---

Mac codesign Upload Errors (90046), (90045), (90211)

Solution: Provisioning profile issue.

---

Can Previous JSON Config Be Used for Next Obfuscation?

Solution: Yes.

---

Error: .error: re-sign failed, Please check whether the ipa package is arm architecture exit status 2; all “No” selected; IPA generated but cannot install

Solution: The re-sign module may be faulty. Set both re-sign and install test options to “No” and click Start Processing. The tool will generate an unsigned obfuscated IPA. Manually re-sign using Mac codesign. For installation testing, connect the device via USB or Wi-Fi and ensure the IPA is re-signed. Install test function is tied to the re-sign module; if the module fails, automatic installation will not work.