Unable to save to gdrive
See original GitHub issueError: Service Unavailable
{
"status": 503,
"method": "POST",
"url": "/api/newGoogle/"
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (9 by maintainers)
Top Results From Across the Web
why I get the message: can't save to Drive? - Google Support
Go to file -> Save as Google Slides · Go to file -> Make a copy · Go to file -> Download (may...
Read more >10 Common Google Drive Issues (And How to Solve Them)
1. Check Google Drive's Online Status · 2. Disable Your Antivirus and Firewall · 3. Restart Google Drive.
Read more >Can't save to Drive > All changes can still be found from File ...
In order to solve it, I opened Google Drive in a new tab and ensured to be able to see all files and...
Read more >How to fix Google Drive not downloading files - Setapp
Quite frequently the Google Drive not downloading can be attributed to your browser's settings, specifically to it saving something incorrectly ...
Read more >Let's Solve Google Docs Not Saving Changes or Comments ...
If there is a temporary problem with your Google Drive server, your Google application may not be able to connect to its server,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Crash is occurring in
/new
on line 168 after attempting to save, becausebody
is undefined if saving fails:https://github.com/naturalcrit/homebrewery/blob/3cf5dc74bbb2d8ca010bb822bf67c762d52be6e3/client/homebrew/pages/newPage/newPage.jsx#L156-L168
We need to:
Gracefully handle that error. Exit the function if
body
is empty and post up a better message to the user without crashing (similar to what we already have in theedit
page)Investigate why the Google brew fails to save in the first place. Doesn’t look like a “login” issue otherwise we would get an error 401 and we would see
Not signed in!
Seems to be a 403 “insufficient credentials” thingAlso, apparently I already ran into this error (or a similar error) earlier this year (stackoverflow) but I can’t find a relevant issue opened on Github.
Yes I am, thanks for the quick solution!