Google App Engine Seach Java not working since this morning: com.google.appengine.api.search.SearchException: Error constructing stub for app

57 views
Skip to first unread message

Bruno Schuermans

unread,
Jan 18, 2019, 3:13:44 PM1/18/19
to Google App Engine
Hello

My application was running fine in app engine. spec: Java8 standard.
Than since this morning I get this exception when I try to use the SearchService: com.google.appengine.api.search.SearchException: Error constructing stub for app

I have noted that Java7 is not supported from today but I am using Java8 Standard environment.

Anybody has encontered the same problem?

Akash Eldo

unread,
Jan 20, 2019, 2:45:43 PM1/20/19
to Google App Engine
Hi Bruno,

I've had the exact same problem. My application was working until yesterday(1/19) when I tried adding some documents to the index. I got this error:
 PutException: Error constructing stub for app

I then tried to use my search endpoint to search documents already in the index and I got the same SearchException you did.

davidc...@google.com

unread,
Jan 21, 2019, 4:01:50 PM1/21/19
to Google App Engine

Hello Bruno and Akash,


Since Google Groups is meant for conceptual discussions and this is a report about an issue with the platform, please create a Google Issue Tracker and include all the relevant information since Issue Tracker is the right place to report issues about the Google Cloud platform.


George (Cloud Platform Support)

unread,
Jan 21, 2019, 5:26:31 PM1/21/19
to Google App Engine
Hi Bruno, 

We need your project ID, to investigate this specific error further. You should not write private information such as project IDs in public forums, but you can reply to me privately using the drop-down menu of the top-right reply button, and choosing "reply privately to author". Your help is much appreciated. 

George (Cloud Platform Support)

unread,
Jan 22, 2019, 5:40:11 PM1/22/19
to Google App Engine
You may follow issue 123192346 to monitor progress and eventual fixes. No estimated time to resolution has been set. Engineering is already working towards a fix.
Reply all
Reply to author
Forward
0 new messages