Highlighted

Why AIR_64 Helper and ExtendedAppEntryTemplate64 creates so much problem?

Explorer ,
Sep 14, 2016

Copy link to clipboard

Copied

Recently we were in process to submit our AIR application to App Store and we soon flooded with lots of problem signing it and then in uploading process. Following were many problems we have faced with these two newly introduced executable in AIR SDK 64-bit version.

1. If we decide NOT to delete these two files in application signing process, we'll get following message at the time of signing .app file:

[exec] DEPLOY/xxx.app: code object is not signed at all

2. If we decide to delete these two files, then signing .app file became successful (following message) but it broke some particular feature like opening Terminal window and running command in it by an AppleScript or ExpectScript file (by NativeProcess):

[exec] DEPLOY/xxx.app: signed bundle with Mach-O thin (x86_64) [net.xxx.xxx]

3. We also faced such errors while uploading a build to iTunesConnect which is overwhelming:

1 package(s) were not uploaded because they had problems:

/var/folders/1b/8qtyjnc154jfq_5bysrxcht40000gv/T/55EA97A7-5A0A-4540-A715-C0B46D63044F/1099109346.itmsp - Error Messages:

ERROR ITMS-90296: "App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: [( "xxx.pkg/Payload/xxx.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR_64 Helper", "xxx.pkg/Payload/xxx.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/ExtendedAppEntryTemplate64" )] Refer to App Sandbox page at https://developer.apple.com/devcenter/mac/app-sandbox/ for more information on sandboxing your app."

Why we have so much problem with these two particular file?

Why we're having 'Code object not signed at all' message if we decide NOT to delete these two files in signing phase?

Why iTunesConnect will report about these two suspicious files which actually supplied by Adobe with their SDK - when no other executable reported likewise?

Thank you.

TOPICS
Performance issues

Views

282

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Why AIR_64 Helper and ExtendedAppEntryTemplate64 creates so much problem?

Explorer ,
Sep 14, 2016

Copy link to clipboard

Copied

Recently we were in process to submit our AIR application to App Store and we soon flooded with lots of problem signing it and then in uploading process. Following were many problems we have faced with these two newly introduced executable in AIR SDK 64-bit version.

1. If we decide NOT to delete these two files in application signing process, we'll get following message at the time of signing .app file:

[exec] DEPLOY/xxx.app: code object is not signed at all

2. If we decide to delete these two files, then signing .app file became successful (following message) but it broke some particular feature like opening Terminal window and running command in it by an AppleScript or ExpectScript file (by NativeProcess):

[exec] DEPLOY/xxx.app: signed bundle with Mach-O thin (x86_64) [net.xxx.xxx]

3. We also faced such errors while uploading a build to iTunesConnect which is overwhelming:

1 package(s) were not uploaded because they had problems:

/var/folders/1b/8qtyjnc154jfq_5bysrxcht40000gv/T/55EA97A7-5A0A-4540-A715-C0B46D63044F/1099109346.itmsp - Error Messages:

ERROR ITMS-90296: "App sandbox not enabled. The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list: [( "xxx.pkg/Payload/xxx.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Adobe AIR_64 Helper", "xxx.pkg/Payload/xxx.app/Contents/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/ExtendedAppEntryTemplate64" )] Refer to App Sandbox page at https://developer.apple.com/devcenter/mac/app-sandbox/ for more information on sandboxing your app."

Why we have so much problem with these two particular file?

Why we're having 'Code object not signed at all' message if we decide NOT to delete these two files in signing phase?

Why iTunesConnect will report about these two suspicious files which actually supplied by Adobe with their SDK - when no other executable reported likewise?

Thank you.

TOPICS
Performance issues

Views

283

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Sep 14, 2016 0

Have something to add?

Join the conversation