Multiple Cloud Endpoint API versions in the same Appengine Version.

[Francis Mwangi]

I have an android app in alpha stage that I am testing how I will be managing updates both in the server and client side..

 

First release to users. My android is using generated classes from this base cloud endpoint class and deployed to the default Appengine version.

@Api(name = "myAPIName", version = "v1

public class AbstractEndpoint<T>{

}

 

<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">

   <application>myapp</application>

   <module>default</module>

   <version>1</version>

</appengine-web-app>

2nd Release

I increment the Api version from V1 to V2 and use the generated classes in my for my 2nd app release. I deploy the backend to the same default appengine version 1.

@Api(name = "myAPIName", version = "v2

public class AbstractEndpoint<T>{

}

 

<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">

   <application>myapp</application>

   <module>default</module>

   <version>1</version>

</appengine-web-app>

The problem is that after the upgrade only the latter client apps using v2 can cases the Appengine endpoint v2 and those using V1 can no longer access the api v1. Either V2 overwrites V1 or  both v1 and V2 cannot run in the same Appengine instance or something else..

Have tried combing the documentation, and stack overflow for clues with no much success.

[Adam (Cloud Platform Support)]

This is exactly what is expected. You're only changing the API version number and deploying over the same (default) App Engine version. There is nothing in the docs to suggest that this would create two versions of your API which would serve at the same time from the same instance.

If you need to serve two different API versions at once, you need to also deploy to a new App Engine version. Alternatively, you can use two different projects.