CODEWITHSUNDEEP
pythongoogle-app-engine
John
John

Reputation: 1486

This application does not exist (app_id=xxx)

I was unable to upload to an AppEngine as appcfg was telling me :

This application does not exist (app_id=u'xxx').

I was only a developer on the AppEngine, so as I was just testing I created a new AppEngine where I was the owner but I still get the same message on a newly created AppEngine.

Upvotes: 24

Views: 19870

Answers (13)

chaduhduh
chaduhduh

Reputation: 80

I had this issue and I simply needed to run 'gcloud app create' for this project within the console console. Screenshot

Previously I don't think this step was needed.

Upvotes: 0

user2738183
user2738183

Reputation: 

appcfg.py --no_cookies --oauth2 --email=myemail --noauth_local_webserver  update .

I navigated to my app engine directory folder and ran the above command. This deployed it successfully from the command line for me (Mac OSX terminal)--although I still couldn't deploy from app engine launcher. I believe Launcher still thinks I'm running off port 8080. However, running dev_appserver.py --port=11080 .doesn't fix this issue for me-- what ended up solving it was just removing the directory from the app engine launcher then just re-adding it.

Upvotes: 1

ObiHill
ObiHill

Reputation: 11886

Posting Ric Moore's comment in the selected answer because that is a valid answer and it worked in my case (and hopefully it helps someone else having the same issue spot it quickly).

I have an alternation solution - in the Google App Engine Launcher select from the menu Control > Clear Deployment Credential. Then when you click Deploy it will take you through the auth flow again and you can select the correct account. - Ric Moore

Upvotes: 0

Aditya
Aditya

Reputation: 630

What worked for me is to use the project id from the google app engine console instead of the project name in app.yaml

Upvotes: 0

David T.
David T.

Reputation: 23429

The fix I found was to add the parameter --no_cookies:

appcfg.py update --no_cookies MyProjectDirectory/

This can happen when you upload AppEngine applications from different Google accounts on the same computer.

Upvotes: 42

tamalet
tamalet

Reputation: 657

If you are using --oauth2 make sure that you are logged into the correct account when generating the token.

Upvotes: 1

JulianDavid
JulianDavid

Reputation: 123

I fixed this problem by editing my app.yaml file to have the correct application name. In the app.yaml file where it says 'application:[insert app name here]', I had to change the [insert app name here] part. I'm not sure why the name was wrong, but I do remember toying around with it before while attempting to fix a different bug. The way I figured out the proper name was to go to my applications in my GAE admin console and look to see what the app's name was there. Hope this helps anyone else that runs into this same problem :)

Upvotes: 1

Charles Young
Charles Young

Reputation: 106

This is really old, so I wouldn't be surprised if this isn't picked up by the poster, but I wanted to ensure that I have a reference for the next time I have the issue.

I had this issue. My problem ended up being that I had not invited the user that I was authenticating as to be a developer on the project. In fact I had just created the user and not even logged on yet.

I logged on to the google infrastructure as the new user, then added the new user as a developer on the application. I was then able to upload the app.

Upvotes: 4

crushingaction
crushingaction

Reputation: 11

this way worked:

  1. modified the app.yaml to specify the application: some_id
  2. python appcfg.py update ../some_application/server/python

Upvotes: 1

Sarah Northway
Sarah Northway

Reputation: 1068

The same problem occurs with the Java/Eclipse plugin version of App Engine. The 404 happens when you're logged in to the wrong Google account from within the plugin. In that case, look at the bottom-left of Eclipse to see what account you're currently using.

Regarding the Python command line updater, if your cookies indicate that you're logged in to a Google account that doesn't have access to the application you're updating, then that would explain why ignoring those cookies by using "appcfg.py update --nocookies" fixes it.

Upvotes: 5

osantana
osantana

Reputation: 7187

I got the same error message trying to make the first deployment of a Python Application using a Google Apps account.

In my case the problem was caused by the fact that my 2-way authentication is enabled.

With 2-way authentication enabled you need to generate an authentication password in your Google Account Management Application and use it to do the deployments.

Upvotes: 1

John
John

Reputation: 1486

Tried to upload to the app this morning (first time i've tried since Friday) and it just worked (first time...!)

No idea what the issue was as I haven't done any work on this over the weekend so everything should have been the same as it was on Friday.

Upvotes: 1

Hassek
Hassek

Reputation: 8995

You have to log in in your gae account and create an application before you upload it, and your app_id has to have the same name as you app. You can't just upload it.

So go here, create your app, for example "example_app" and set the app_id=example_app and everything should work :)

Upvotes: 12

Related Questions