Authentication error on Windows: ...alameda_bundle.min-vflHAZfb_.js

[Andrey S.1]

Recently my app users started reportig this problem with Dropbox authentication:

 "An error has occured in the script of this page  https://cfl.dropboxstatic.com/static/compiled/js/alameda_bundle/alameda_bundle.min-vflHAZfb_.js"

Also see a complete descriptionon the same issue from another developer here:

https://stackoverflow.com/questions/50087272/oauth-2-script-error#

[Greg-DB]

Thanks for the report! I added a comment there. 

For reference, per the official documentation, you should process this in the system browser, and not a web view. In addition to supporting the Google Sign In flow per Google's requirements in the future, that will offer the best compatibility with the Dropbox site in general.

Anyway, while I can't promise a fix for web view, we will investigate. A few more pieces of information would be helpful though:

- the exact name and version of the underlying browser used by the web view

- any JavaScript errors from the page

[Andrey S.1]

It's a .NET WPF-based app, which uses Dropbox.NET (https://github.com/dropbox/dropbox-sdk-dotnet)

There are no means to authenticate in a system's default browser. So, I have to use the web view.

I jave no information about the Java version. But it's all Windows 10 users.

[Greg-DB]

Thanks! We'll look into it.

[Andrey S.1]

There is another issue. Now it takes more than 20 seconds for the auth page to render. No matter what internal browser is used WebBrowser or CefSharp. The same URL loads immediately in a standalone Chrome browser, but has same almost 20 seconds delay in Microsoft Edge.

Here is an example URL:

https://www.dropbox.com/oauth2/authorize?response_type=token&client_id=ovbydhrxqbsjkqc&redirect_uri=...

[Greg-DB]

To clarify, are you seeing this in the standalone Microsoft Edge browser as well, or only in any web view based on Microsoft Edge?

It would be useful to know if you're seeing this in the standalone browser. I just tried it in standalone Microsoft Edge and it loaded much quicker than that for me.

[Andrey S.1]

I saw this in a standalone Edge browser earlier today, but now this delay is gone somehow. Did you do any changes on your side?

[Greg-DB]

Thanks for letting me know! I'm glad to hear that's no longer occurring. I'm not aware of any such changes, so it may have just been a transient issue.