You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Michael-X-Net edited this page Feb 3, 2023
·
1 revision
#When deploying GAE, the appid is in use, causing the deployment to fail
##Phenomenon:
There is already an appid available, assuming the name is xagent
After XX-Net releases a new version, set xagent as the current working appid, and then deploy xagent, and the deployment will fail at this time
##reason:
During the deployment process, Google App Engine needs to suspend the work of the old version of the appid, and then enable the new version.
After suspending the old version, while the new version is not enabled, XX-Net cannot communicate with Google App Engine, resulting in deployment failure.
##solution:
If there are multiple appids, you can set one as the current working appid, deploy other appids, and then rotate to deploy this appid.
If not, don’t fill in the appid first, the system will use the preset appid, and use your own appid after the deployment is successful.
##Many appids are used and deployed:
There is a certain probability of success, and there may be problems, depending on luck.