[google-appengine] Re: Datastore Viewer broken - URGENT.
Issue created http://code.google.com/p/googleappengine/issues/detail?id=8164 -Aswath On Sat, Sep 22, 2012 at 2:17 AM, Peter McKenzie peter...@google.com wrote: Please create a bug on the issue tracker. On Friday, September 21, 2012 11:43:49 PM UTC+10, aswath wrote: Further narrowing down on the issue. If there are fewer namespaces in the app-id, then a dropdown is shown to select the namespace. Then everything is fine for the app-id. However, if there are large number of namespaces in the app-id, then the suggest box is shown. While select the namespace here and browsing, then we are not able to view the entities in the namespace. -Aswath On Fri, Sep 21, 2012 at 7:08 PM, Aswath Satrasala aswath.s...@gmail.comwrote: Hello All, In the admin console, click on the datastore viewer. * Start typing the namespace name * Select the namespace name The KINDS are shown in the dropdown. After doing this, earlier, the namespace text field was shown above. Now, this is missing. I select the KIND from the dropdown, then it says there are no entities in the empty namespace. Anyone facing this issue? I cannot seen any entities in any namespace -Aswath -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Google App Engine SDK 1.7.2 is out
Thanks Takashi and everyone on the GAE team. It's great to see how many bugfixes you squeezed in, and I'd like to applaud the effort! Keep it up. Shiny new toys get people more excited and are probably harder to justify to certain stakeholders, but as a customer I can sleep a lot better at night knowing that quality is high on your agenda. Releases like this give me the confidence I need to be recommending GAE to others again. So kudos to you all for such a boring yet bold release! :) Cheers, Per On Thursday, September 20, 2012 12:26:40 PM UTC+2, Takashi Matsuo (Google) wrote: Hi everyone, We're happy to announce that we released the 1.7.2 SDK. This release includes several new features including the trusted tester program of App Engine outbound socket, as well as huge amount of bug fixes. For more details, please read our blog post and release notes. Announcement: http://googleappengine.blogspot.com.au/2012/09/app-engine-172-released.html Release notes for Java: http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes Release notes for Python: http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Enjoy! -- Takashi Matsuo | Developers Advocate | tma...@google.com javascript: -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Mn75qzVakQAJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Google App Engine SDK 1.7.2 is out
Totally agree. Awesome release. I'm really happy to see so many bugs fixed in a single release. Keep it coming! -- alex On Sun, Sep 23, 2012 at 11:35 AM, Per per.fragem...@gmail.com wrote: Thanks Takashi and everyone on the GAE team. It's great to see how many bugfixes you squeezed in, and I'd like to applaud the effort! Keep it up. Shiny new toys get people more excited and are probably harder to justify to certain stakeholders, but as a customer I can sleep a lot better at night knowing that quality is high on your agenda. Releases like this give me the confidence I need to be recommending GAE to others again. So kudos to you all for such a boring yet bold release! :) Cheers, Per On Thursday, September 20, 2012 12:26:40 PM UTC+2, Takashi Matsuo (Google) wrote: Hi everyone, We're happy to announce that we released the 1.7.2 SDK. This release includes several new features including the trusted tester program of App Engine outbound socket, as well as huge amount of bug fixes. For more details, please read our blog post and release notes. Announcement: http://googleappengine.blogspot.com.au/2012/09/app-engine-172-released.html Release notes for Java: http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes Release notes for Python: http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Enjoy! -- Takashi Matsuo | Developers Advocate | tma...@google.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Mn75qzVakQAJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Google App Engine SDK 1.7.2 is out
Here here! It's really great to see a lot of these longstanding issues closed. Kudos to the team -- new features are great, but making the old features work better is best! Jeff On Sun, Sep 23, 2012 at 3:42 AM, alex a...@cloudware.it wrote: Totally agree. Awesome release. I'm really happy to see so many bugs fixed in a single release. Keep it coming! -- alex On Sun, Sep 23, 2012 at 11:35 AM, Per per.fragem...@gmail.com wrote: Thanks Takashi and everyone on the GAE team. It's great to see how many bugfixes you squeezed in, and I'd like to applaud the effort! Keep it up. Shiny new toys get people more excited and are probably harder to justify to certain stakeholders, but as a customer I can sleep a lot better at night knowing that quality is high on your agenda. Releases like this give me the confidence I need to be recommending GAE to others again. So kudos to you all for such a boring yet bold release! :) Cheers, Per On Thursday, September 20, 2012 12:26:40 PM UTC+2, Takashi Matsuo (Google) wrote: Hi everyone, We're happy to announce that we released the 1.7.2 SDK. This release includes several new features including the trusted tester program of App Engine outbound socket, as well as huge amount of bug fixes. For more details, please read our blog post and release notes. Announcement: http://googleappengine.blogspot.com.au/2012/09/app-engine-172-released.html Release notes for Java: http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes Release notes for Python: http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Enjoy! -- Takashi Matsuo | Developers Advocate | tma...@google.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Mn75qzVakQAJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Why latest is not a valid version name anymore?
Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why latest is not a valid version name anymore?
You can always set the *default* to whatever version you have deployed. What's wrong with that? On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 iaco...@fastwebnet.it wrote: Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why latest is not a valid version name anymore?
I can't do that, since i need to update the version that is called *latest*. If i try doing that, by setting the version to *latest* in my yaml file, even if the version *latest* already exists, the server replies i can't have a version called *latest*. Moreover the default version (version called *1*) serves an older version of my app that still has a couple of users. On Sunday, September 23, 2012 8:20:46 PM UTC+2, alex wrote: You can always set the *default* to whatever version you have deployed. What's wrong with that? On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 iac...@fastwebnet.itjavascript: wrote: Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. To post to this group, send email to google-a...@googlegroups.comjavascript:. To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFxAzMjD3dkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why latest is not a valid version name anymore?
Upload a new version, e.g. mynewawesomeversion and set the default to that so that users will access your app at myapp.appspot.com (or a custom domain) and not latest.myapp.appspot.com. It's the best approach, I believe. latest has a special meaning for app versions routing. If you have some changes that you can't make backward compatible with mobile client, you could always do something like myapp.appspot.com/v1/... and /v2/... I believe it's much better than making your mobile client connect to a specific version-based subdomain. -- alex On Sun, Sep 23, 2012 at 8:28 PM, Iaco86 iaco...@fastwebnet.it wrote: I can't do that, since i need to update the version that is called *latest*. If i try doing that, by setting the version to *latest* in my yaml file, even if the version *latest* already exists, the server replies i can't have a version called *latest*. Moreover the default version (version called *1*) serves an older version of my app that still has a couple of users. On Sunday, September 23, 2012 8:20:46 PM UTC+2, alex wrote: You can always set the *default* to whatever version you have deployed. What's wrong with that? On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 iac...@fastwebnet.it wrote: Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFxAzMjD3dkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why latest is not a valid version name anymore?
I probably wasn't clear. latest.myapp.appspot.com always points to the, well, latest deployed *default* version. Say, if you have deployed awesome.myapp.appspot.com and make it default version, then accessing latest.myapp.appspot.com will actually route internally to awesome.myapp.appspot.com anyway. It's like an alias. On Sun, Sep 23, 2012 at 8:43 PM, alex a...@cloudware.it wrote: Upload a new version, e.g. mynewawesomeversion and set the default to that so that users will access your app at myapp.appspot.com (or a custom domain) and not latest.myapp.appspot.com. It's the best approach, I believe. latest has a special meaning for app versions routing. If you have some changes that you can't make backward compatible with mobile client, you could always do something like myapp.appspot.com/v1/... and /v2/... I believe it's much better than making your mobile client connect to a specific version-based subdomain. -- alex On Sun, Sep 23, 2012 at 8:28 PM, Iaco86 iaco...@fastwebnet.it wrote: I can't do that, since i need to update the version that is called *latest*. If i try doing that, by setting the version to *latest* in my yaml file, even if the version *latest* already exists, the server replies i can't have a version called *latest*. Moreover the default version (version called *1*) serves an older version of my app that still has a couple of users. On Sunday, September 23, 2012 8:20:46 PM UTC+2, alex wrote: You can always set the *default* to whatever version you have deployed. What's wrong with that? On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 iac...@fastwebnet.it wrote: Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFxAzMjD3dkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why latest is not a valid version name anymore?
Ok, thanks a lot for this info: didn't know that ;) Now it's much clearer: just had to reconfigure server in order to kindly ask older version users to update to the new version, thus giving minimal downtime period. Thanks a lot. Cheers, Iacopo On Sunday, September 23, 2012 8:53:26 PM UTC+2, alex wrote: I probably wasn't clear. latest.myapp.appspot.com always points to the, well, latest deployed *default* version. Say, if you have deployed awesome.myapp.appspot.com and make it default version, then accessing latest.myapp.appspot.com will actually route internally to awesome.myapp.appspot.com anyway. It's like an alias. On Sun, Sep 23, 2012 at 8:43 PM, alex al...@cloudware.it javascript: wrote: Upload a new version, e.g. mynewawesomeversion and set the default to that so that users will access your app at myapp.appspot.com (or a custom domain) and not latest.myapp.appspot.com. It's the best approach, I believe. latest has a special meaning for app versions routing. If you have some changes that you can't make backward compatible with mobile client, you could always do something like myapp.appspot.com/v1/... and /v2/... I believe it's much better than making your mobile client connect to a specific version-based subdomain. -- alex On Sun, Sep 23, 2012 at 8:28 PM, Iaco86 iac...@fastwebnet.itjavascript: wrote: I can't do that, since i need to update the version that is called *latest*. If i try doing that, by setting the version to *latest* in my yaml file, even if the version *latest* already exists, the server replies i can't have a version called *latest*. Moreover the default version (version called *1*) serves an older version of my app that still has a couple of users. On Sunday, September 23, 2012 8:20:46 PM UTC+2, alex wrote: You can always set the *default* to whatever version you have deployed. What's wrong with that? On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 iac...@fastwebnet.it wrote: Hi everyone, I have a version of my python appengine server that is named latest. This is the version used by the web applications that interface with the service. Now it looks like I can't update anymore the version, since Google suddently decided that latest is not a valid version name anymore... Can anyone tell me why? Since I use the server for a mobile app, I will have a 10 days blackout on my app, since the server is not working anymore and i can't update it anymore. I will therefore have to deploy a new version of the server, with a different name, deploy a new version of my mobile application and wait for it to be certified. Why couldn't google allow the version name anymore? It is causing a major hassle + lot of negative votes on the market Thanks for replies. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFxAzMjD3dkJ. To post to this group, send email to google-a...@googlegroups.comjavascript:. To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/NbZXF5RmMtQJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Google App Engine SDK 1.7.2 is out
Thanks On 9/23/12, alex a...@cloudware.it wrote: Totally agree. Awesome release. I'm really happy to see so many bugs fixed in a single release. Keep it coming! -- alex On Sun, Sep 23, 2012 at 11:35 AM, Per per.fragem...@gmail.com wrote: Thanks Takashi and everyone on the GAE team. It's great to see how many bugfixes you squeezed in, and I'd like to applaud the effort! Keep it up. Shiny new toys get people more excited and are probably harder to justify to certain stakeholders, but as a customer I can sleep a lot better at night knowing that quality is high on your agenda. Releases like this give me the confidence I need to be recommending GAE to others again. So kudos to you all for such a boring yet bold release! :) Cheers, Per On Thursday, September 20, 2012 12:26:40 PM UTC+2, Takashi Matsuo (Google) wrote: Hi everyone, We're happy to announce that we released the 1.7.2 SDK. This release includes several new features including the trusted tester program of App Engine outbound socket, as well as huge amount of bug fixes. For more details, please read our blog post and release notes. Announcement: http://googleappengine.blogspot.com.au/2012/09/app-engine-172-released.html Release notes for Java: http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes Release notes for Python: http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Enjoy! -- Takashi Matsuo | Developers Advocate | tma...@google.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Mn75qzVakQAJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] IE/Opera + Dev Server = slow, problematic
I can't use IE or Opera for testing with development server (local). - For some reason some of the scripts/images don't load. For the ones that load, it takes a huge amount of time for them to load compared to Firefox/Chrome. - When you make a request, it takes some time for it to show up on the logs. (IE is much much worse than opera) Do you have similar experiences? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/KIit8eKcfMkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Unable to update: java.lang.RuntimeException: Version not ready
I have the same issue for like a week till now. The chance of getting through is like 30%. On Friday, September 14, 2012 11:45:04 AM UTC-7, Aneetha Venu wrote: Hi, All of a sudden since today morning, whenever I try to deploy my app to a particular application in googleplex.com (concierge.googleplex.com), I keep getting the following error Unable to update: java.lang.RuntimeException: Version not ready. at com.google.appengine.tools.admin.AppVersionUpload.commit(AppVersionUpload.java:569) at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:143) at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:328) at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:52) at com.google.appengine.tools.admin.AppCfg$UpdateAction.execute(AppCfg.java:725) at com.google.appengine.tools.admin.AppCfg.init(AppCfg.java:188) at com.google.appengine.tools.admin.InternalAppCfg.init(InternalAppCfg.java:21) at com.google.appengine.tools.admin.InternalAppCfg.main(InternalAppCfg.java:17) com.google.appengine.tools.admin.AdminException: Unable to update app: Version not ready. at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:333) at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:52) at com.google.appengine.tools.admin.AppCfg$UpdateAction.execute(AppCfg.java:725) at com.google.appengine.tools.admin.AppCfg.init(AppCfg.java:188) at com.google.appengine.tools.admin.InternalAppCfg.init(InternalAppCfg.java:21) at com.google.appengine.tools.admin.InternalAppCfg.main(InternalAppCfg.java:17) Caused by: java.lang.RuntimeException: Version not ready. at com.google.appengine.tools.admin.AppVersionUpload.commit(AppVersionUpload.java:569) at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:143) at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:328) ... 5 more I have tried to deploy my app nearly about 10 times today and it still gives me the same result. However, I am able to deploy to any other application. I am not sure how to proceed. I need this application name for a concierge project. Kindly help. Thanks, Aneetha -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/0ShrLfCAcyoJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
