| Issue 712: | Error message when launching app engine: The Google App Engine Runtime could not be extracted | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Full message: The Google App Engine Runtime could not be extracted (perhaps you are running the Launcher from the dmg? If so, drag copy the Launcher to your local disk first.) GoogleAppEngineLauncher.app may not work correctly. I am running it from the application folder, not the dmg. I saw this in the console log: 2008-09-18 16:31:12.772 GoogleAppEngineLauncher[1752] *** -[NSCFArray addObject:]: attempt to insert nil What steps will reproduce the problem? 1. Double click on GoogleAppEngineLauncher Does this problem exist with both the SDK app server and our production app servers? Just the SDK. What is the expected output? What do you see instead? To be able to use google app engine as I could with the older version. What version of the product are you using? On what operating system? 1.1.3 on mac os x 10.4.11 Please provide any additional information below. |
|
,
Sep 19, 2008
(No comment was entered for this change.)
Status: WontFix
|
|
,
Jan 18, 2009
Same problem to me. What version of the product are you using? On what operating system? 1.1.8 on mac os x 10.5.6 |
|
,
Jan 20, 2009
It was a weird permissions issue on the application folder - happened with other apps as well. I solved it by creating another admin user and shifting everything to that. |
|
,
Feb 19, 2009
Same for me. v.1.1.9 on mac osx 10.5.6. Tried to tweak permissions without success.. |
|
,
Oct 13, 2009
Just had this upgrading from 1.2.5 to 1.2.6 on both leopard and snow leopard. I run as a non-admin user. The install for 1.2.5 worked fine - but for 1.2.6 I had this error. I tracked it to the stage that it couldn't extract /Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine- default.bundle/Contents/Resources/google_appengine.zip since that lowest Resources directory was owned by root. Unzipping it as root by hand didn't work either - but - changing the Resources dir (again - the lowest level one here) to give all users write access solved the issue for me. A hack, but at least I can work today ;) |
|
,
Nov 27, 2009
Same issue over here as chrisdsearle. I'm on Leopard 10.6.2 and installed the latest 1.2.7. I am logged in as a non-admin. I copied the Launcher from the dmg to my Applications folder. Running the Laucher from there gave the same error message. If I copy the Launcher to my Desktop folder, It launches just fine, but that's not the location I like to keep it... |
|
|
|