iOS build installation failed

[ichark]

Hi!
Thanks for the quick fix on the previous ticket.
There is still an issue with installing the build.
It shows the following error:
ERROR: Install failed. Got error "ApplicationVerificationFailed" with code 0xe8008001: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.LKaRe5/extracted/Payload/es_ios_c.app/Frameworks/AppLovinSDK.framework : 0xe8008001 (An unknown error has occurred.)

[marchbold]

Can you tell me what your build environment is?

Issues like this are normally signing related. Currently you should be using macOS with AIR SDK 50.2+ (preferrably 51.+) and an iOS SDK 18+ to build applications.

[ichark]

Yes, it is correct. We are using the following settings:

• macOS (Sonoma 14.5)
• AIR SDK 51.1.3.2
• iPhoneOS 18.2.sdk

[marchbold]

Are you using native signing (i.e. what are the settings in your adt.cfg or AIR SDK Manager)?

And just confirming that you are passing the iOS SDK path when packaging, either via -platformsdk, in your adt.cfg or via the AIR SDK Manager?

[ichark]

I build projects using IntelliJ IDEA, where I specify the path to the Apple iOS SDK.
I recently changed the values in adt.cfg:
Set UseNativeCodesign=true
Specified the path to iOSPlatformSDK
Unfortunately, the result remains the same – the build cannot be installed on the device.

[marchbold]

Have you added your developer certificate to keychain on your machine?

[IvakhnenkoDmytro]

Hi all,
I have the same issue with my build and found out that in the AppLovin framework plist, the MinimumOSVersion is set to 100.0. Could this be the reason for the issue?

[jdtapslots]

We are experiencing the same issue — iOS builds fail to install with ApplicationVerificationFailed / 0xe8008001 after updating from ANE-IronSource 3.9.1 to 4.1.0. This appears to be a regression.

Expected behaviour

iOS IPA packages with AppLovinSDK.framework in the Frameworks directory, signs correctly via ADT, and installs on device — as it did with ANE-IronSource 3.9.1.

Actual behaviour

IPA builds successfully but fails at install time:

ERROR: Install failed. Got error "ApplicationVerificationFailed" with code 0xe8008001:
Failed to verify code signature of .../Payload/MainIOS.app/Frameworks/AppLovinSDK.framework :
0xe8008001 (An unknown error has occurred.)

Key finding: The same AppLovinSDK.framework (v12.6.0, unchanged binary) installs correctly with com.distriqt.IronSource.ane 3.9.1 but fails with 4.1.0. The framework itself is not the variable — the updated IronSource core ANE triggers the signing failure.

What we tested (all failed with 4.1.0 core ANE):

1. Old framework binary (12.6.0) — fails
2. New framework binary (13.1.0) from 4.1.0 distribution — fails
3. Removing _CodeSignature from AppLovinSDKResources.bundle — fails
4. Removing Info.plist from resource bundle and storyboardc — fails
5. Stripping LC_CODE_SIGNATURE from Mach-O binary — fails
6. Minimal framework (binary + Info.plist only) — fails
7. Removing framework entirely — installs (but crashes due to missing dylib)

Truncated binary in distribution: The AppLovinSDK Mach-O binary shipped in ANE-IronSource-4.1.0 (assets/ios/Frameworks/AppLovinSDK.framework/AppLovinSDK) is 5,239,168 bytes, but its LC_CODE_SIGNATURE load command references a 72,048-byte code signature starting at offset 5,239,168 — the signature data is missing. The complete binary should be 5,311,216 bytes. While this may not be the direct cause (AIR re-signs anyway), shipping a truncated binary with a dangling LC_CODE_SIGNATURE reference is problematic and may compound the signing issue.

Re: MinimumOSVersion 100.0 (mentioned by @IvakhnenkoDmytro in #76): This value is present in both the old 12.6.0 framework (which signs correctly with 3.9.1 ANEs) and the new 13.1.0, so it is not the cause of the signing failure.

Environment

• AIR SDK version: 51.2.2.6
• Device OS: iOS
• Device version: iPhone
• Development IDE: VSCode
• Development OS: Windows 11
• Native codesigning: Not available (Windows)

Workaround

Split ANEs by platform — iOS uses old 3.9.1 ANEs (ane/ios/), Android uses updated 4.1.0 ANEs (ane/android/). iOS stays on older mediation SDK versions until this is resolved.

Related

• Can't install iOS build with the latest version of AppLovin ane  #67 (same issue, closed — resolved via native codesigning on macOS, not applicable to Windows)
• adt package: iOS .ipa with dynamic frameworks fails to sign when assets with Info.plist files are included (storyboards etc) airsdk/Adobe-Runtime-Support#144 (open — ADT signing fails with dynamic frameworks containing Info.plist assets)
• iOS Dynamic Libraries not signed correctly airsdk/Adobe-Runtime-Support#521 (closed — original dynamic framework signing fix)

[marchbold]

Linking on Windows will always be an issue with updates as the SDKs progress with the iOS SDK version but the linker often trails. I highly recommend considering macOS as a development environment for iOS.

Are you using a recent iOS SDK when building and have you tried using the llvm toolchain? https://airsdk.dev/docs/tutorials/platform/ios/windows-packaging

[jdtapslots]

Thanks for the response. To clarify our setup: we use remote linking (ADT's RemoteLinkMachine feature) — the linker runs on macOS via SSH, but IPA packaging and code signing still happen on Windows via ADT's Java-based signer. Native codesigning is not available in this configuration.

That said, the core issue remains: the same AppLovinSDK.framework signs and installs correctly when paired with the 3.9.1 IronSource core ANE, but fails with 4.1.0 — same build environment, same signing pipeline, same framework binary. Something changed in the 4.1.0 ANE that triggers a signing edge case in ADT's Windows packager.

We're working around it by splitting ANEs per platform (4.1.0 for Android, 3.9.1 for iOS) but would appreciate any insight into what changed in the 4.1.0 core ANE that might affect framework signing behavior.