简体   繁体   English

App Engine:端点未更新

[英]App Engine: Endpoints not updated

I wrote 2 endpoints with Google App Engine, which run flawlessly on localhost. 我使用Google App Engine编写了2个终结点,它们可以在localhost上完美运行。 Let their names be A and B. 假设它们的名称为A和B。

Now I wanted to add push functionality (GCM + APNS). 现在,我想添加推送功能(GCM + APNS)。 So I downloaded the Mobile Backend Starter code from Google ( https://github.com/GoogleCloudPlatform/solutions-mobile-backend-starter-java ) and integrated that code into my project (which I am developing using Android Studio). 因此,我从Google( https://github.com/GoogleCloudPlatform/solutions-mobile-backend-starter-java )下载了Mobile Backend Starter代码,并将该代码集成到我的项目中(我正在使用Android Studio开发)。 This adds two endpoint classes EndpointV1 and BlobEndpoint. 这将添加两个端点类EndpointV1和BlobEndpoint。 So far, so good. 到现在为止还挺好。

Now whenever I run and deploy my code it seems to work normally: 现在,每当我运行和部署我的代码时,它似乎都能正常工作:

./gradlew backend:appengineRun
./gradlew backend:appengineUpdate

The update is successful, too: 更新也成功:

# ... building ...
5% Scanning for jsp files.               
20% Scanning files on local disk.        
25% Initiating update.                   
28% Cloning 2 static files.              
31% Cloning 33 application files.        
40% Uploading 2 files.                   
52% Uploaded 1 files.                    
61% Uploaded 2 files.                    
68% Initializing precompilation...       
73% Sending batch containing 2 file(s) totaling 2KB.
90% Deploying new version.               
95% Will check again in 1 seconds.       
98% Will check again in 2 seconds.       
99% Will check again in 4 seconds.       
99% Will check again in 8 seconds.       
99% Will check again in 16 seconds.      
99% Closing update: new version is ready to start serving.
99% Uploading index definitions.         

Update for module default completed successfully.
Success.                                 
Cleaning up temporary files for module default...

BUILD SUCCESSFUL

Total time: 1 mins 9.457 secs

The version gets deployed and I can see that it is successfully updated online (I am also using the correct version). 该版本已部署,我可以看到它已成功在线更新(我也在使用正确的版本)。 But whatever I do, it has completely hidden the endpoint B in the API Explorer - but the new endpoints for push are shown. 但是无论我做什么,它已经在API资源管理器中完全隐藏了端点B-但是显示了用于推送的新端点。

Moreover, I now reverted to my old code locally (no push endpoints). 而且,我现在在本地恢复了我的旧代码(没有推送端点)。 And the push endpoints are still shown in the API Explorer. 推送端点仍显示在API Explorer中。

Am I completely missing something here? 我在这里完全错过了什么吗? What am I doing wrong if the endpoints show up on localhost flawlessly? 如果端点完美地显示在本地主机上,我该怎么办?

After getting some sleep the new API showed up just the next morning. 睡一觉之后,第二天早上就出现了新的API。 So it seems it was an internal issue with App Engine. 因此,看来这是App Engine的内部问题。 If you have the same problem: 如果您有同样的问题:

  1. Just wait a couple of hours for the problem to fix itself 只需等待几个小时即可解决问题
  2. or (better) open a support case for this problem and link your project ID. 或(更好)打开此问题的支持案例并链接您的项目ID。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM