Getting the error as
"responses": [
{
"error": {
"code": 4,
"message": "image-annotator::RPC deadline exceeded.: Backend timeout!"
}
}
]
while trying to use OCR through vision APIs
Related
I'm currently trying to send a notification using the " Try this API " interface of Firebase.
I filled my Request Body with this :
{
"validateOnly": false,
"message": {
"notification": {
"body": "Body",
"title": "Title"
}
}
}
and the RequestParameters with
projects/myprojectid
I didn't check the Google API Key since my project doesn't have one, but I checked the Google OAuth 2.0.
After executing, I get this error :
{
"error": {
"code": 400,
"message": "Recipient of the message is not set.",
"status": "INVALID_ARGUMENT",
"details": [
{
"#type": "type.googleapis.com/google.rpc.BadRequest",
"fieldViolations": [
{
"field": "message",
"description": "Recipient of the message is not set."
}
]
},
{
"#type": "type.googleapis.com/google.firebase.fcm.v1.FcmError",
"errorCode": "INVALID_ARGUMENT"
}
]
}
}
After some research, I don't understand what is missing in the request. Are all the parameters mandatory for the request ?
You're not specifying who the message is for, which is what the error message is trying to tell you. You can do by either including a token key with one of more device tokens, or a topic or condition key in the JSON.
Also see the Firebase documentation on building requests to send a message for more information and examples of each of these.
I am trying to subscribe to all user's calendars, but some calendars do not support this functionality.
Request:
POST https://www.googleapis.com/calendar/v3/calendars/{calendarId}/events/watch
Response:
{
"error": {
"errors": [
{
"domain": "calendar",
"reason": "pushNotSupportedForRequestedResource",
"message": "Push notifications are not supported by this resource."
}
],
"code": 400,
"message": "Push notifications are not supported by this resource."
}
}
How I can find out whether the current calendar support "watch"?
Does it corresponding to "accessRole" from calendar#calendarListEntry.accessRole
New users trying to setup logins that aren't #google.com are hitting issues using Google Identity Toolkit. This has been working fine for a long time so not sure what's up. Looks like this:
In the console seeing a 500 error coming back when calling this URL:
https://www.googleapis.com/identitytoolkit/v3/relyingparty/setAccountInfo?key=<key>
POST data:
{"email":"nlckeweo#sharklasers.com","displayName":"test","password":"password"}
API response:
{
"error": {
"code": 500,
"message": "Internal error encountered.",
"errors": [
{
"message": "Internal error encountered.",
"domain": "global",
"reason": "backendError"
}
],
"status": "INTERNAL"
}
}
I have created a calendar list on the Google Calendar API. I have a job scheduler running on a server which it will add new events to the calendar list using Service Account. It was working fine previously, but recently I keep on receiving HTTP Code 500 Backend Error when adding a new event.
Tried exponential backoff solution and Google APIs Explorer, none of them works.
Here's the request and response from the APIs Explorer,
Request
POST https://www.googleapis.com/calendar/v3/calendars/{MY_CALENDAR_LIST_ID}%40group.calendar.google.com/events?key={YOUR_API_KEY}
{
"end": {
"dateTime": "2016-07-29T14:00:00",
"timeZone": "Europe/London"
},
"start": {
"dateTime": "2016-07-29T12:00:00",
"timeZone": "Europe/London"
},
"reminders": {
"useDefault": true
},
"summary": "Some Title of the Event",
"description": "Some Description for the Event",
"location": "London"
}
Response
null
{
"error": {
"code": -1,
"message": "A network error occurred, and the request could not be completed."
}
}
Our application using google-identity-toolkit for authentication is receiving a 500 "backendError" from the verifyAssertion API. This occurs about 30% of the time and started happening about 1 week ago. 70% of the time the call succeeds. Our app has not changed in 6 months. Is there a broken server out there in the pool somewhere?
Error message:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "backendError",
"message": "Backend Error"
}
],
"code": 500,
"message": "Backend Error"
}
}