Highlighted

AIR 20 permission error on OSX when new runtime tries to rename *_32

Explorer ,
Dec 13, 2015

Copy link to clipboard

Copied

As part of the AIR 20 release notes (AIR 64 bit on Mac OS X) - All new applications created by AIR developers will be running on this 64 big Runtime on Mac OSX, and all the existing shared, captive, and native applications will continue to work on this 64 bit Runtime on Mac OS X - any application built with earlier AIR SDK than 20 should work on newer Runtime, however there is scenario when the process gets into permission trap because of it's ways.

We have multiple AIR applications for both Windows and OSX. After updating to AIR 20 64 bit Runtime on OS X, several were continue to work expectedly except one. Our steps were as follows:

  1. We were running on AIR 19 and application ABC was working fine
  2. Install AIR 20.0.0.204
  3. ABC does not launch anymore

Doing investigation, we ran ABC manually in Terminal and its getting a permissions error on startup. It seems that AIR is automatically creating another copy of the executable with "_32" appended. However, ABC was installed as root, so this action gave a permissions error.

We were able to fix this with a chmod, but this is probably not an appropriate solution for the users.

We do not know why or how ABC was installed as root in the first place, but we should consider this a scenario, too.

Following is the Terminal output when we tried to run ABC after updating our OS X to AIR 20 Runtime:

host-camacminiprominicnet:~ joelanderson$ cd /ABC.app/

host-camacminiprominicnet:ABC.app joelanderson$ cd Contents/MacOS/

host-camacminiprominicnet:MacOS joelanderson$ ls

ABC

host-camacminiprominicnet:MacOS joelanderson$ ./ABC

2015-12-10 12:33:31.285 ABC[39131:34345711] renaming from

/Applications/ABC.app/Contents/MacOS/ABC to

/Applications/ABC.app/Contents/MacOS/ABC_32

2015-12-10 12:33:31.311 ABC[39131:34345711] renaming failed with this error: Error Domain=NSCocoaErrorDomain Code=513 "“ABC” couldn’t be moved because you don’t have permission to access “MacOS”." UserInfo=0x5079a0 {NSSourceFilePathErrorKey=/Applications/ABC.app/Contents/MacOS/ABC, NSUserStringVariant=(

  Move

), NSFilePath=/Applications/ABC.app/Contents/MacOS/ABC, NSDestinationFilePath=/Applications/ABC.app/Contents/MacOS/ABC_32, NSUnderlyingError=0x507670 "The operation couldn’t be completed. Permission denied"}

Checking the permission of ABC:

host-camacminiprominicnet:MacOS joelanderson$ ls -lah

total 72

drwxr-xr-x@ 2 root wheel 102B Dec 9 05:34 .

drwxr-xr-x@ 4 root wheel 204B Dec 9 05:34 ..

-rwxr-xr-x@ 1 root wheel 34K Feb 2 2015 ABC

host-camacminiprominicnet:MacOS joelanderson$ ls -lah ..

total 16

drwxr-xr-x@ 4 root wheel 204B Dec 9 05:34 .

drwxr-xr-x@ 3 root wheel 102B Dec 9 05:34 ..

-rwxr-xr-x@ 1 root wheel 1.4K Dec 9 05:34 Info.plist

drwxr-xr-x@ 2 root wheel 102B Dec 9 05:34 MacOS

-rwxr-xr-x@ 1 root wheel 8B Feb 2 2015 PkgInfo

drwxr-xr-x@ 6 root wheel 272B Dec 9 05:34 Resources

Compared to EFG which works fine after updating to AIR 20 Runtime:

host-camacminiprominicnet:MacOS joelanderson$ ls -lah

total 144

drwxr-xr-x@ 2 joelanderson staff 136B Dec 10 12:29 .

drwxr-xr-x@ 4 joelanderson staff 204B Jun 4 2015 ..

-rwxr-xr-x@ 1 joelanderson staff 32K Nov 22 01:24 EFG

-rwxr-xr-x@ 1 joelanderson staff 34K Feb 2 2015 EFG_32

host-camacminiprominicnet:MacOS joelanderson$ ls -lah ..

total 16

drwxr-xr-x@ 4 joelanderson staff 204B Jun 4 2015 .

drwxr-xr-x@ 3 joelanderson staff 102B Jun 4 2015 ..

-rw-r--r--@ 1 joelanderson staff 1.3K Jun 4 2015 Info.plist

drwxr-xr-x@ 2 joelanderson staff 136B Dec 10 12:29 MacOS

-rw-r--r--@ 1 joelanderson staff 8B Feb 2 2015 PkgInfo

drwxr-xr-x@ 6 joelanderson staff 272B Jun 4 2015 Resources

Since AIR 20 Runtime creating it's own 64 bit executable and renaming existing executable as "_32" can turns error in different system. Renaming a root installed executable is one of such scenario, there could be more which we don't know yet. This is clear that if the permissions were always correct, this wouldn't be a problem. But since we can't rely on them being correct, apparently, we think we needs some valid steps to overcome such problem.

The only way we're seeing at this moment is if earlier AIR SDKs provide some ways to package our DMG/PKG with multiple executable (_32 and _64), then we might not have above like situation; new Runtime need not to create/rename executable and gets into any possible permission error. Though I am not sure about the feasibility, but we surely need some fix.

TOPICS
Air beta

Views

902

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

AIR 20 permission error on OSX when new runtime tries to rename *_32

Explorer ,
Dec 13, 2015

Copy link to clipboard

Copied

As part of the AIR 20 release notes (AIR 64 bit on Mac OS X) - All new applications created by AIR developers will be running on this 64 big Runtime on Mac OSX, and all the existing shared, captive, and native applications will continue to work on this 64 bit Runtime on Mac OS X - any application built with earlier AIR SDK than 20 should work on newer Runtime, however there is scenario when the process gets into permission trap because of it's ways.

We have multiple AIR applications for both Windows and OSX. After updating to AIR 20 64 bit Runtime on OS X, several were continue to work expectedly except one. Our steps were as follows:

  1. We were running on AIR 19 and application ABC was working fine
  2. Install AIR 20.0.0.204
  3. ABC does not launch anymore

Doing investigation, we ran ABC manually in Terminal and its getting a permissions error on startup. It seems that AIR is automatically creating another copy of the executable with "_32" appended. However, ABC was installed as root, so this action gave a permissions error.

We were able to fix this with a chmod, but this is probably not an appropriate solution for the users.

We do not know why or how ABC was installed as root in the first place, but we should consider this a scenario, too.

Following is the Terminal output when we tried to run ABC after updating our OS X to AIR 20 Runtime:

host-camacminiprominicnet:~ joelanderson$ cd /ABC.app/

host-camacminiprominicnet:ABC.app joelanderson$ cd Contents/MacOS/

host-camacminiprominicnet:MacOS joelanderson$ ls

ABC

host-camacminiprominicnet:MacOS joelanderson$ ./ABC

2015-12-10 12:33:31.285 ABC[39131:34345711] renaming from

/Applications/ABC.app/Contents/MacOS/ABC to

/Applications/ABC.app/Contents/MacOS/ABC_32

2015-12-10 12:33:31.311 ABC[39131:34345711] renaming failed with this error: Error Domain=NSCocoaErrorDomain Code=513 "“ABC” couldn’t be moved because you don’t have permission to access “MacOS”." UserInfo=0x5079a0 {NSSourceFilePathErrorKey=/Applications/ABC.app/Contents/MacOS/ABC, NSUserStringVariant=(

  Move

), NSFilePath=/Applications/ABC.app/Contents/MacOS/ABC, NSDestinationFilePath=/Applications/ABC.app/Contents/MacOS/ABC_32, NSUnderlyingError=0x507670 "The operation couldn’t be completed. Permission denied"}

Checking the permission of ABC:

host-camacminiprominicnet:MacOS joelanderson$ ls -lah

total 72

drwxr-xr-x@ 2 root wheel 102B Dec 9 05:34 .

drwxr-xr-x@ 4 root wheel 204B Dec 9 05:34 ..

-rwxr-xr-x@ 1 root wheel 34K Feb 2 2015 ABC

host-camacminiprominicnet:MacOS joelanderson$ ls -lah ..

total 16

drwxr-xr-x@ 4 root wheel 204B Dec 9 05:34 .

drwxr-xr-x@ 3 root wheel 102B Dec 9 05:34 ..

-rwxr-xr-x@ 1 root wheel 1.4K Dec 9 05:34 Info.plist

drwxr-xr-x@ 2 root wheel 102B Dec 9 05:34 MacOS

-rwxr-xr-x@ 1 root wheel 8B Feb 2 2015 PkgInfo

drwxr-xr-x@ 6 root wheel 272B Dec 9 05:34 Resources

Compared to EFG which works fine after updating to AIR 20 Runtime:

host-camacminiprominicnet:MacOS joelanderson$ ls -lah

total 144

drwxr-xr-x@ 2 joelanderson staff 136B Dec 10 12:29 .

drwxr-xr-x@ 4 joelanderson staff 204B Jun 4 2015 ..

-rwxr-xr-x@ 1 joelanderson staff 32K Nov 22 01:24 EFG

-rwxr-xr-x@ 1 joelanderson staff 34K Feb 2 2015 EFG_32

host-camacminiprominicnet:MacOS joelanderson$ ls -lah ..

total 16

drwxr-xr-x@ 4 joelanderson staff 204B Jun 4 2015 .

drwxr-xr-x@ 3 joelanderson staff 102B Jun 4 2015 ..

-rw-r--r--@ 1 joelanderson staff 1.3K Jun 4 2015 Info.plist

drwxr-xr-x@ 2 joelanderson staff 136B Dec 10 12:29 MacOS

-rw-r--r--@ 1 joelanderson staff 8B Feb 2 2015 PkgInfo

drwxr-xr-x@ 6 joelanderson staff 272B Jun 4 2015 Resources

Since AIR 20 Runtime creating it's own 64 bit executable and renaming existing executable as "_32" can turns error in different system. Renaming a root installed executable is one of such scenario, there could be more which we don't know yet. This is clear that if the permissions were always correct, this wouldn't be a problem. But since we can't rely on them being correct, apparently, we think we needs some valid steps to overcome such problem.

The only way we're seeing at this moment is if earlier AIR SDKs provide some ways to package our DMG/PKG with multiple executable (_32 and _64), then we might not have above like situation; new Runtime need not to create/rename executable and gets into any possible permission error. Though I am not sure about the feasibility, but we surely need some fix.

TOPICS
Air beta

Views

903

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
Dec 13, 2015 0
Adobe Employee ,
Dec 14, 2015

Copy link to clipboard

Copied

HI ,

This issue is known to us and we are working on it .

As a workaround ,please follow the below mentioned steps to resolve the issue :-

  1. Uninstall the installed application from the system
  2. Download AIR 20 (Adobe - Adobe AIR)
  3. Re-install the application .

Please let me know if you still face any issue .

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
Reply
Loading...
Dec 14, 2015 0
Participant ,
Dec 15, 2015

Copy link to clipboard

Copied

I upgraded to AIR 20.  Now, when I try to access Adobe Media Player, the programme refuses to load.  The console window is showing the same error message as above.  I assume that the failure to load AMR is related to the issue reported here.

I was unsure about the suggested workaround.  Am I supposed to uninstall AIR 20?  When I ran the uninstaller, I got a warning that about 15 Adobe products would no longer work if I proceeded.  So, I stopped.  Do I go ahead and remove AIR 20 and then, following the re-install, these products will start working again?

Or, am I supposed to uninstall my target application (Adobe Media Player)?  If I do that, I can't re-install AIR 20 because I get a warning that it is already installed.  So, I assume that the process is to uninstall AIR 20.  But, that is leaving me very nervous.

I would appreciate reassurance about the process and the potential of adverse effects on the products which rely on AIR 20.

Thank you.

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
Reply
Loading...
Dec 15, 2015 0
Adobe Employee ,
Dec 15, 2015

Copy link to clipboard

Copied

HI ,

Please uninstall and reinstall the application Adobe Media Player.

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
Reply
Loading...
Dec 15, 2015 0
Participant ,
Dec 15, 2015

Copy link to clipboard

Copied

Maybe a dumb question but: How?

I can delete Media Player by dragging it to the trash (I'm on an iMac BTW).  But, there is no 'uninstall' option that i can find.  And, if I do delete it, I don't have a copy of package required to in-install it.  And, having searched the Adobe site, I can't find any page that will let me re-download the programme.

I would appreciate further advice.

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
Reply
Loading...
Dec 15, 2015 0
Adobe Employee ,
Dec 15, 2015

Copy link to clipboard

Copied

HI ,

On Mac, you will not get an uninstall option. Simply drag the application from "Applications" to Trash .

Please try downloading the Adobe Media Player from the link: Flash Media Playback.

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
Reply
Loading...
Dec 15, 2015 0
Participant ,
Dec 15, 2015

Copy link to clipboard

Copied

I've already been on the page you mention but can not find a download link for Adobe MEDIA player.  The page is for Adobe FLASH player (which, I think, is a browser-based player, not a stand-alone application like Media player).  In any event, the download for neither product works.

If I click on the 'try' button, I get taken to a blog page (Open Source Media Framework Blog | Adobe’s free and open source media playback system‌ ) the last posting of which was in 2012.  That posting sends me to SourceForge (OSMF - Browse Files at SourceForge.net) which appears to provide zip files of the source code for the media projects.  These are not suitable for re-installing anything, unless you are prepared to go through a full compilation of the course code (which is beyond my interest and skills).

I have a Creative Cloud membership but Media Player doesn't show up in the installation options.  I have checked the Adobe 'discontinued software' page but Media Player isn't listed there.  I do still have the CD4 and CS5 DVDs and may be able to find an old copy on those disks. But,.....

When I checked the Adobe Media Player forum on Adobe's site (Adobe Media Player).  It states that Media Player is no longer available for download.

How am I supposed to fix the mess which the AIR 20 has made of using this software?  I regularly use Media player to view videos downloaded from the web for later viewing.  I also use it to preview videos I am making using Camtasia for educational purposes.

PS.  I tried the 'change the permissions' approaches mentioned in the first post above.  That has got the Media Player running again.  But, it is clearly not an optimal approach to have to use.

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
Reply
Loading...
Dec 15, 2015 0
Explorer ,
Dec 16, 2015

Copy link to clipboard

Copied

Hi Nitanwar, thank you for your answer. At least now we know Adobe aware of this problem.

We distribute ours applications to our clients, and we updated them with easy application updater system that AIR provides. The solution that you suggested is not intuitive. However, if Adobe wouldn't come up with a fix sooner, we may have no choice but to ask them to go through this non-intuitive process.

Does this has an issue report in Adobe bugbase? Else I'll create one to keep us informed.

Thanks you.

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
Reply
Loading...
Dec 16, 2015 0
Explorer ,
Dec 20, 2015

Copy link to clipboard

Copied

I've created a bug report to bugbase Adobe on this. But I have no URL to the report since I reported this as Security Issue:

As bugbase mentioned:

"Thank you for submitting a bug. Due to security concerns, this bug will not be externally viewable."

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
Reply
Loading...
Dec 20, 2015 0