Sample App Deployment Issue: Latest SDK Version not supported

[Stephan Hofmann]

Hi all,

I tried to deploy the example app from the Google Developer Console to the App Engine. 

The first error I'm getting is:

********************************************************

The API version in this SDK is no longer supported on the server!

-----------

Latest SDK:

Release: 1.9.26

Timestamp: Tue Jul 28 12:00:50 PDT 2015

API versions: [1]

-----------

Your SDK:

Release: 1.9.26

Timestamp: Wed Aug 12 11:30:50 PDT 2015

API versions: [1.0]

-----------

Please visit https://developers.google.com/appengine/downloads for the latest SDK.

********************************************************

After that, it keeps telling me that the App Id could not be found:

Sep 28, 2015 1:49:06 PM com.google.appengine.tools.admin.AbstractServerConnection send1

WARNING: Error posting to URL: https://appengine.google.com/api/appversion/getresourcelimits?app_id=aetest-1082&version=1&

404 Not Found

This application does not exist (app_id=u'aetest-1082').

#####

Your help is much appreciated.

Best regards,

Stephan

[Nick (Cloud Platform Support)]

Hey Stephan,

This is a known issue, and you can safely ignore the message. There was just a thread about this the other day. It should disappear in a future SDK release. In general, you should always be sure to update your SDK to the latest release, although that's not the problem here and as said, you can rest assured knowing there's nothing wrong with your system.

Best wishes,

Nick

[Stephan Hofmann]

Thanks Nick.

That means I have to keep digging, as my app is actually NOT deploying.

Best,

Stephan

[Nick (Cloud Platform Support)]

Hey Stephan,

Apologies, I had missed the lower part of the output. The error message you see usually results when the project in question is not owned or deployable for the account you've auth'd to the SDK with. If you're using appcfg, try deleting ~/.appcfg_oauth2_tokens or ~/.appcfg_oauth2_tokens_java. If you're using the gcloud, try running gcloud auth list to see which account you're auth'd as. It could also result from a mis-spelling of the app id, so check that as well.

[Nick (Cloud Platform Support)]

Hey Stephan,

Any luck with attempting to fix your auth, or make sure the app id is right?

On Tuesday, September 29, 2015 at 12:04:08 AM UTC-4, Stephan Hofmann wrote:

[Stephan Hofmann]

Hi Nick,

sorry, just came back from a short trip.

Yes, it’s working now after deleting the oauth file. 

Still need to understand “why”, but I will look into the documentation and see if I can find more details here.

Thanks for your help. Much appreciated.

Br,

Stephan 

-- 
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/3Mw-30SGrlI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/fddcea36-4453-444c-9613-a4c2e56f0826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nick (Cloud Platform Support)]

It's possible the stored oauth credentials were for another developer account which doesn't have access to that project? 

To unsubscribe from this group and all its topics, send an email to google-appengine+unsub...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.