I have an issue with Android Management API when trying to create/patch a WebApp with an icon. If the imageData is not correct, the API returns a detailed error but if the imageData is encoded as expected, the API returns a HTTP 503 error code with message "The service is currently unavailable.". I thought this error would be transient but the REST calls seem to always fail. Any information could be helpful.
This error usually occurs when adding icons on AMAPI webApps. This issue is still pending in our Engineering’s backlog, Unfortunately, we have no shareable timeline or additional info.
If you want to stay up to date with the latest updates for Android enterprise, we suggest that you join the Android Management API mailing list to receive monthly updates and service advisories directly to your inbox.
The API has been fixed. We no longer have this problem.
Related
I need to use the GMB API to get review data but I get the following error.
Google My Business API has not been used in project 341557982028 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/mybusiness.googleapis.com/overview?project=341557982028 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
When I click on the link I get "failed to load" (see image attached). I enabled all the APIs (8 or 9) but still doesn't work. I completed the form and got the authorization from Google from the app already. Location data is working fine.
I really need help with this one!
This is strange we have started receiving too many per day (nearly 300-500 times)
googleapi: Error 500: Internal error encountered., backendError
while calling Admin SDK Directory API. https://developers.google.com/admin-sdk/directory
Google chat support for API is removed and Facing issue with how to address the problem. Our rate limit and query calls are way in the limits. We query Admin SDK as a cronjob schedule.
Is there a way we can debug 500 errors for AdminSDK
Is there any information regarding which deployment Region of Google is more capable to handle load?
No error on console
Logs error
Contact Workspace Support or File a Bug
As DalmTo pointed out, 500 errors are usually out of your control. Especially in this case since you are calling Google's servers.
The best option to debug these errors is probably contacting support directly. You can find the corresponding contact information for your Workspace account on this page.
https://support.google.com/a/answer/1047213?hl=en
If you are able to regularly reproduce this and you think its a bug, fill out the template here:
https://issuetracker.google.com/issues/new?component=191635&template=824102
Ensure to include your code, complete reproduction steps, some evidence/statistics of the failures, and any other information you can give.
This usually happens when the Google Cloud Platform service account used for authentication was created after the in-app products.
To solve this, make a trivial edit to your in-app products in the Google Play Console. For example, add a temporary tag. Then try again to make the request and it should succeed.
By the way, the same is true for the purchases.voidedpurchases which reports an "insufficient permissions" error.
I'm building a Go client service for google analytics reporting v4, but my report calls respond with the 403 error re: unused API, with a link in the err to auth the api.
I'm using the precise same service json, view id, etc in a redash data source though with no problem.
Clearly, the API is authorized.
Are there any other factors at play, perhaps in the go client or a version mismatch (redash using v3, vs go using v4)?
Worth noting:
when I go through the motions to authorize the api, even if i try to auth-cycle it (turn it off and on), console.google gives me a ui error re: blank referrals are ignored.
the acct and project are definitely linked correctly (per the auth link taking me to right project id)
I think I found it, and it sort of comes down to a version mismatch: I found a new API in the console named "Google Analytics Reporting API" for v4, which is not "Analytics API" that I'd been using.
It's a little confusing because I was trusting the auth link in the error message, which took me to the already-authorized v3 API. At the same time, I feel like this would have been a non-issue if I'd read the migration docs more closely.
We try to call the API API_BUSINESS_PARTNER via our Java application. The Java implementation communicates with a SAPUI5 - Front End application, so that the data can be displayed via an app.
Through our On - Premise System it works without any problems and we also get back data. But via the application we get the error "No error field found in JSON" and the SCP - Log for ODataConnectivityUtil shows us that the respective user is not authorized.
Accordingly we tried to call an older one MMIM_MATERIAL_DATA_SRV and it works without any problems. We get the same error message in API_PRODUCT_SRV. So it doesn't seem to work with the new APIs in general.
Thank you,
best regards.
The error message
Our source code
Logging snippet
Thanks again for the support.
We have solved the problem now.
The problem is that the first metadata request is executed on the default client (client 100) although we have set "sap-client=200" in the destination configuration.
Our passwords between the clients were different, so we received an authentication error.
We suspect that the "newer" API's will not be able to access the configuration for the destination from the SCP. So it probably worked with the older ones.
One problem for us was that the Cloud SDK does not take the client from the destination configuration (for the metadata request).
The other problem was that the error message "No error field found in JSON" was misleading.
Only by the tip with "ODataConnectivityUtil", we could see our authentication error. So thanks again.
Which version of the S/4HANA Cloud SDK are you using? This might be an issue that we had in an older version. Could you update to the latest release version and give it a try again?
Details on releases can be found here:
https://sap.github.io/cloud-s4-sdk-examples/release-notes/
Hint: I would also suggest to use our virtual data model classes that we provide for invoking such OData services. You can find a blog post on this topic here: https://blogs.sap.com/2017/05/21/step-4-with-sap-s4hana-cloud-sdk-calling-an-odata-service/
Pls take a look in the S/4HANA OData log which you can find using transaction /iwfnd/error_log (put /n before it).
Then you execute the OData call to provoke the error. If you then find an entry in the OData log, it does mean that the authentication to S/4HANA was succesful. Also then you would figure out mor error details.
In case you do not find any entry, it is very likely that you are not authenticating correctly. In this case S/4HANA returns 401 and an HTML document as response payload.
From the Google API Console: When trying to change the Billable Limits for the project under the Quota page, I keep getting the error: Your input was invalid.
The error message is not very informative, doesn't specify which input was invalid or why it was invalid.
I've experimented with this in IE, Firefox, and Chrome. I've also turned off all other APIs except for Custom Search API (which I'd like to increase the limit for) without any luck.
Has anyone else encountered this problem? how can it be solved?
(response from a Google employee)
This can happen if a "restricted" API is enabled on the project. "Restricted" APIs can only be seen by specifically enabled users. For instance, the Google Maps Javascript API v2 has been marked "restricted" because it was retired in 2013, and no user should see this API anymore (and instead, use v3).
Work is underway to remove the Google Maps Javascript API v2 from all the existing projects. A systemic fix is being worked on (internal Google reference #12001333), but in the meantime, if you see this error, the best workaround is to use a different API project.