Error in upload java web application error message This application does not exist (app_id=u'xxxxxxx')

[SOHRAB HOSSAIN]

I have just created an sample java webapplication intended for Google
Application Engine. The application runs correctly in my local machine
but using the eclipse plugin I failed to upload the project in the
Google Application Engine ended up with the following error


java.io.IOException: Error posting to URL:
https://appengine.google.com/api/appversion/create?app_id=japaneseguestbook&version=1&
404 Not Found
This application does not exist (app_id=u'japaneseguestbook').

PLZ. help

NB. The gmail account I am using for application is new.

[Robert Kluin]

Did you register the appid at appspot.com?

> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>

[msanztru]

Hi all,

I am having exactly the same issue. The id exists in appengine and it matches the contents of the xml file, but having tried several times I always get the same issue....

any ideas?

Thanks!!

[adat...@gmail.com]

I have the same issue aswell

[Junxi Xie]

I'm having this problem as well. But I can successfully upload a Python project to the same app-id. And still, I've just registered the app-id. Perhaps we have to wait for some time so that the Java feature is enabled?

在 2011年5月20日星期五UTC+8下午9时04分20秒，SOHRAB HOSSAIN写道：

在 2011年5月20日星期五UTC+8下午9时04分20秒，SOHRAB HOSSAIN写道：

[Junxi Xie]

Problem solved!

Finally, I managed to solve this problem.

I guess this has something to do with authorization, perhaps appcfg loaded mismatching account information from your cookie. So my solution is simply by adding the '-e' parameter after appcfg, to tell the command line to use the email account you give as the parameter:

appcfg -e your...@gmail.com update X:\Path\to\war

But note that you may need to make sure this is NOT caused by your app creation. You can go to the dashboard to check your app's status, or you can simply upload another project, a Python one, to see if that would be OK.

I hope my post will be helpful to all the users having the same problem.

在 2011年5月20日星期五UTC+8下午9时04分20秒，SOHRAB HOSSAIN写道：

[Bendanpa]

I got this issue today too. I first deployed some apps using one google account, Then when I tried to deploy another app (under different google account) I got this issue. I suspect that this is due to google server has some sort of cache or cookie set to remember user account. When deploy a different app with different account this authorization issue happens. I guess this issue will disappear after certain amont of time without any deploys or ip address changed. But of course, use -e email definitely solved this issue, and next deploys do not need -e email any more.

Thanks for posting the solution.

Cheers,
Bendanpa