TransWikia.com

Google Drive API Console: Error saving Drive UI integration page

Stack Overflow Asked by Marco Carnazzo on December 23, 2021

I have a webapp in production that interacts with Google Drive through Google Drive API.

I need to change some settings in Drive interaction but I can’t save.

When I save the Drive UI integration page, I receive this error:

There’s a problem at our end.

Please try again. If the problem persists, please let us know using
the “Send feedback” link below. Thanks!

(spying Network console: there is an Internal Server Error in a POST call)

I tried to send feedback for months: nobody answers and the bug is still there.

I tried also to create another project: I can save the first time but then the bug returns.

How can I do? Has someone the same problem?

Is there a way to receive a reply from Google? Is there some workaround?

Thank you.

2 Answers

For myself trying to get the Drive UI configured I noticed a couple of errors (that don't have any specific error messages)

  1. When adding in an Open URL it has to be a valid domain, so for instance I tried to test it out with local host, to no avail. However something like https://devbox.app.com worked, but something like https://localhost:8888 does not. Even though https://localhost is a valid javascript origin in the client_id configuration (at least for the app I am working on, not sure about other apps), localhost doesn't work as an open URL.
  2. When adding in the mimeTypes it needs to be in the format */* and can include custom mimeTypes like application/custom+xml and application/custom-name+json not sure for other custom types that are not in a particular format like xml or json. Also not sure about wildcards.
  3. When adding in file extensions do not add in the '.' just the name of the file extension.
  4. The app icon I found only failed to upload the image when the image wasn't the exact dimensions, I actually ended up editing some icons in photoshop to change the pixel x pixel values as a quick work around during dev.

That worked for me to get it to save and I tested it with a file that had a custom mimeType (application/custom-name+xml specifically) and custom file extension!

Answered by Maplefury on December 23, 2021

i think that problem must be Client ID

before adding Client ID, go to the Credentials -> OAuth 2.0 Client IDs then select edit your Client ID. after that your production site url add to Authorized JavaScript origins and Authorized redirect URIs.

then enter your Client ID in Drive UI integration page

Answered by Tharindu Vindula on December 23, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP