-
Notifications
You must be signed in to change notification settings - Fork 0
Error: Authorization page could not be loaded on Dropbox #15
Comments
It's definitely not a wrong or missing redirect URL: when outputting the auth URL and following the link, Dropbox asks to connect to Owl. Besides, Dropbox gives an error page when using an invalid redirect URL. I think it's an issue with newer versions of Chrome, potentially API changes. |
I tried with Dropbox SDK JS; same thing, though I still relied on chrome.identity.launchWebAuthFlow. Maybe that's where the issue is. |
FWIW, Tusk works on Firefox 72.0.2 Build ID 20200117190643 |
Chromium Team found the error - Turns out that param |
I'm still getting this problem using Vavaldi, details below.
|
@rustyjarz Thanks for the info, I'll try and look into it this week. |
I just tested it and I can reproduce it on Vivaldi Stable:
Also repro case on Chrome Stable:
However, Dropbox works on Chrome Unstable:
|
Also works on Firefox 74 (latest stable) |
https://bugs.chromium.org/p/chromium/issues/detail?id=1049565#c2 Now it's actually a bug in Chromium :D I'll pin this issue again so people are aware. |
Wonderful. So glad chromium people picked this up. Looking forward to using Owl. |
Also working for me within Edge, Version 81.0.416.64. |
Still seeing this error pop up in Chrome 83 on macOS Catalina 10.15.3. I'm gonna double check Chrome Dev. |
Nevermind. If a proper Redirect URI is not set in Dropbox Developer App Console, then Chrome simply drops the OAuth Request and displays "Authorization page could not be loaded". Manually following the URL shows that the bad Redirect URI is the cause. So it finally works with Chrome 83! I'll close this issue. |
Ref subdavis/Tusk#339
Error is reproducible on Chrome Dev Version 81.0.4000.3 (Official Build) dev (64-bit).
In console, the same error is output as in frontend.
The text was updated successfully, but these errors were encountered: