Skip to main content
gennadiyr50003368
Participant
January 6, 2018
Question

Embed dynamic framework

  • January 6, 2018
  • 2 replies
  • 2701 views

At the time of writing this, I have tried with AIR 28 to embed dynamic framework. I followed instruction in release notes 11/16/2017 - Beta - AIR 28.0.0.112

But I have encountered an error at an application install:

Jan  5 17:12:50 **** mobile_installation_proxy(MobileSystemServices)[251] <Notice>: 0x16b3ab000 handle_install: Installation failed: Error Domain=MIInstallerErrorDomain Code=13 "Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.rTdpV9/extracted/Payload/****.app/Frameworks/****.framework : 0xe8008001 (An unknown error has occurred.)" UserInfo={LibMISErrorNumber=-402620415, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=147, FunctionName=+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]

I followed Apple's Technical Note TN2318: Troubleshooting Failed Signature Verification guide, and here are results of verification of used framework after unpacking .ipa file:

****:bin-debug ****$ codesign --verify -vvvv Payload/****.app/Frameworks/****.framework/

Payload/****.app/Frameworks/****.framework/: invalid Info.plist (plist or signature have been modified) In architecture: armv7

But if I check this framework before packaging it is unsigned at all, I tried to take this dynamic framework from working native iOS sample after archiving and unpacking archive but I ended up with the same result.

After some research, by using codesign commands I realized that Info.plist file wasn't included in signing

Info.plist=not bound

Maybe it happened because of this:

"If you are code signing manually, use the --entitlements flag, naming the target’s entitlements property list file:

codesign --entitlements /path/to/entitlements.plist -s <identity> <code-path>

"

Code Signing Tasks

Could you provide some feedback on what's going on and why it doesn't work?

I masked sensitive info by **** symbols

This topic has been closed for replies.

2 replies

Amrita Gangwani
Adobe Employee
Adobe Employee
May 24, 2018

Hi,

The issue has been addressed in our latest beta release. You may download the beta from Download Adobe AIR 30 Beta - Adobe Labs

Thanks!

Known Participant
May 24, 2018

it says Android packaging would remain unaffected.

we need this fix for android too.

also know issues says none ?

you should make some test before writing release notes.

the problem is not solved. have no idea what fixes you did. all binaries

remains unchanged.

On Thu, May 24, 2018 at 7:33 PM, Amrita Gangwani <forums_noreply@adobe.com>

Participating Frequently
January 11, 2018

Hi,

From AIR 28, We have added dynamic framework signing while packaging the application. You can download the latest version of AIR SDK from here.

I have created AIR application which contains swift dynamic framework with AIR 28 at my side and successfully able to install the application. In my case, i have built swift framework in Xcode which also contains info.plist, is unsigned at first. After packaging the application with dynamic framework, it gets successfully signed and installed on device as well.

Just make sure you put your all .frameworks file inside Frameworks folder under app packaging directory, so that application gets signed correctly.

-Sourabh Gupta | Adobe AIR Team

gennadiyr50003368
Participant
January 13, 2018

I use AIR 28 SDK to pack ANE and ios app.

My unzipped IPA structure looks the same as in the picture below:

Swift-IOS-ANE/ipa-unzipped.png at master · tuarua/Swift-IOS-ANE · GitHub

I have folder Frameworks/dynamic.framework in the root of app bundle and I see the framework is signed somehow, but nonetheless, I'm still seeing the following error at installing on a device: 'Failed to verify code signature of ...'

Framework is written in Objective-C

Participating Frequently
January 15, 2018

Hi,

Thanks for reply. Also, make sure while packaging the application, all frameworks and dylibs files should not be signed at all.

It would be great if you can share the sample application with me souguptaATadobeDOTcom.

-Sourabh Gupta | Adobe AIR Team