resource envelope is obsolete (custom omit rules)

266 views
Skip to first unread message

DVR Alarm

unread,
Jun 13, 2016, 1:56:53 PM6/13/16
to CodenameOne Discussions
PLEASE NOTE IN THE FOLLOWING TEXTS THE WORD "[REDACTED]" IS USED TO HIDE TRUE IDENTITY OF SOME KEY INFORMATION FOR SECUTIRY, OVERALL IT SHOULD BE READABLE OTHERWISE

although CN1 builder server was able to produce an iOS release build using production certificate and mobile provisioning profile, but the app deployment failed.  I tried to install the app in two different ways as below.  Following the steps, there are some more information included showing some research I did:

Step 1. from the mobile device used the link received from CN1 upon successful build, it reported the app could not be deployed at this time.  Several iteration of the same step failed with the same message

Step.2.  Downloaded the .ipa file in my MAC and using the apple configurator 2 pushed the .ipa file to connected iPhone and observed the phone log, the app failed installing and got following log message

Jun 13 12:49:19 "[REDACTED]" atc[40] <Error>: 0x16e3eb000 __MobileInstallationInstallForLaunchServices_block_invoke222: Returned error Error Domain=MIInstallerErrorDomain Code=13 "Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.Uck0eQ/extracted/Payload/[REDACTED].app : 0xe8008015 (A valid provisioning profile for this executable was not found.)" UserInfo={LibMISErrorNumber=-402620395, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=142, FunctionName=+[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:], NSLocalizedDescription=Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.Uck0eQ/extracted/Payload/[REDACTED].app : 0xe8008015 (A valid provisioning profile for this executable was not found.)}

So, I figured it must be the provisioning file where the problem is, and extracted the embeded.mobileprovision file from the .ipa file and ran the following commands from the terminal

$ codesign --verify -vvvv -R='anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.1] exists and (certificate leaf[field.1.2.840.113635.100.6.1.2] exists or certificate leaf[field.1.2.840.113635.100.6.1.4] exists)' [REDACTED].app

[REDACTED].app: resource envelope is obsolete (custom omit rules)

again ran to check the provisioning profile

$ cms -D -i ./embedded.mobileprovision

<key>Entitlements</key>
    <dict>
        <key>keychain-access-groups</key>
        <array>
            <string>[REDACTED].*</string>       
        </array>
        <key>get-task-allow</key>
        <false/>
        <key>application-identifier</key>
        <string>[REDACTED]</string>
        <key>com.apple.security.application-groups</key>
        <array>
        </array>
        <key>com.apple.developer.team-identifier</key>
        <string>[REDACTED]</string>
        <key>aps-environment</key>
        <string>production</string>
        <key>beta-reports-active</key>
        <true/>
    </dict>
    <key>ExpirationDate</key>
    <date>2017-04-15T14:19:42Z</date>
    <key>Name</key>
    <string>[REDACTED]</string>
    <key>TeamIdentifier</key>
    <array>
        <string>[REDACTED]</string>
    </array>
    <key>TeamName</key>
    <string>[REDACTED]</string>
    <key>TimeToLive</key>
    <integer>305</integer>
    <key>UUID</key>
    <string>b567e5c5-8228-4526-9c43-17c44dbd1ec6</string>
    <key>Version</key>
    <integer>1</integer>


Once again, I am using release certificate and release mobile provisioning profile,

DVR Alarm

unread,
Jun 13, 2016, 2:27:19 PM6/13/16
to CodenameOne Discussions
I found another related post elsewhere appearing to be hinting towards Xcode build

https://issues.jenkins-ci.org/browse/JENKINS-29165

Shai Almog

unread,
Jun 14, 2016, 12:33:19 AM6/14/16
to CodenameOne Discussions
I'm assuming you generated your own provisioning/p12. Generated debug builds can be installed either via the QR code, email or itunes sync.
If you use our certificate wizard this should work "seamlessly" however we support doing this manually but there are many pitfalls see: http://www.codenameone.com/blog/ios-code-signing-fail-checklist.html
Reply all
Reply to author
Forward
0 new messages