Getting current resource limits….

[NameismyName NameName]

 never get past this stage when attempting to deploy my app….

*** Running appcfg.py with the following flags:

    --no_cookies --email=zzzzzz --passin update

11:20 PM Application: jigsawpicture; version: 1

11:20 PM Host: appengine.google.com

11:20 PM 

Starting update of app: jigsawpicture, version: 1

11:20 PM Getting current resource limits.

I never get to the scanning files… or whatever is next.  it just stops here?  Any suggestions.  Thanks.

[Vinny P]

Hello,

Are you still experiencing this problem? App Engine was having deployment difficulties earlier, but it should be OK by now.

 

-----------------

-Vinny P

Technology & Media Advisor

Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

[David French]

Kept on this for an hour now...

2014-04-04 18:41:40 Running command: "['C:\\Python27\\python.exe', '-u', 'C:\\Program Files (x86)\\Google\\google_appengine\\appcfg.py', '--no_cookies', u'--email=xxxx...@gmail.com', '--passin', 'update', u"C:\\x\\x\\x\\xxr\\David's Amazing Proxy"]"

06:41 PM Application: davidfreelearningtools; version: secureable

06:41 PM Host: appengine.google.com

07:42 PM 

Starting update of app: davidfreelearningtools, version: secureable

07:42 PM Getting current resource limits.

[Vinny P]

If you deploy your application to a different application ID, does the problem still persist?

[Ivo Toman]

Hi, I encountered the same problem - the uploading of my app got frozen at "Getting current resource limits.". 

it all started to work after I turned off Shadowsocks (a reverse proxy). I then refreshed connection and initiated the upload anew. I had to go through google account sign in and authorization for google app engine in a popup window and that was it.

[Nick (Cloud Platform Support)]

Hey All,

Since it's unclear at this point who is still experiencing the issue and who isn't, based on what seems to be a solution in the latest message, I'll say this: please make a public issue tracker issue describing your problem with as much information, logs, and relevant code/config file contents as possible. This will ensure that we can best look into any persistent issues. Otherwise, I hope the solution posted by Ivo above is working for everyone.

Best wishes,

Nick