Skip to main content
Participant
July 12, 2018
Question

two issues in air30,air sdk developers please take a look

  • July 12, 2018
  • 1 reply
  • 649 views

In the process of using air30 to package ipa, I found two issues ,  the air sdk developers  please to confirm whether they do exist.

1. When the dynamic framework is used in ane, although the package ipa can be successful (using the development certificate), the dynamic framework can also be successfully signed, but the error is reported during installation, as follows:

Jul 10 18:42:29 minide-iPad mobile_installation_proxy(MobileSystemServices)[10220] <Notice>: 0x16eea7000 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.vKCmLK/extracted/Payload/cnlz.app/Frameworks/TwitterKit.framework : 0xe8008001 (An unknown error has occurred.)" UserInfo={LibMISErrorNumber=-402620415, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=147, FunctionName=+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:], NSLocalizedDescription=Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.vKCmLK/extracted/Payload/cnlz.app/Frameworks/TwitterKit.framework : 0xe8008001 (An unknown error has occurred.)}

2. When the objectC code in ane uses the @11867269 syntax, for example:

If (@available(iOS 11.0, *)) {

            _imageView.accessibilityIgnoresInvertColors = YES;

       }

Then when you package ipa, you will get an error, as follows:

Undefined symbols for architecture arm64:

  "___isOSVersionAtLeast", referenced from:

      -[TWTRSETweetURLAttachmentView initWithURLAttachment:] in libcom.twitter.ane.twitterANE.a(TWTRSETweetURLAttachmentView.o)

      -[TWTRImageScrollView init] in libcom.twitter.ane.twitterANE.a(TWTRImageScrollView.o)

      -[TWTRSEAccountTableViewCell init] in libcom.twitter.ane.twitterANE.a(TWTRSEAccountTableViewCell.o)

This topic has been closed for replies.

1 reply

Legend
July 12, 2018

1) - Ensure it is actually a Dynamic Framework not a static framework.

     - The Dynamic Framework needs to be packaged in a folder call "Frameworks" with the app to be signed correctly.

    - You need to remove any .bundle files from the framework. And package them with the app separately.

2) See Re: @available in XCode causes Undefined symbols error