Dropbox sign in page shown in SFSafariViewController is hanging

Thanks for the report! A JavaScript error could potentially cause this page and operation to fail. To try to track this down, can you try and see if the same issue occurs on the same page in Safari.app itself on that device?

If so, please enable and use the Web Inspector to connect to Safari on the device. You can use that to get any error(s) from the Console for the page on the device.

HI Greg - thanks alot for the response. When the customer of our app tried connecting to Dropbox in Safari.app and in the Dropbox.app, the connection was successful on this one iPad. The sign-in Dropbox page only hangs when shown from SFSafariViewController on this iPad (his other iPads connect successfully to Dropbox in the SFSafariViewController).

Thanks, Martin

Thanks! Unfortunately it looks like the Web Inspector doesn't work in SFSafariViewController, only Safari.app itself, so we don't have a good way to troubleshoot this.

Please let us know if you start seeing more of this (or if it does start happening in Safari.app as well), but for now I think using Safari.app as a workaround is the best option. Since this only happens in SFSafariViewController, whatever the issue is might be out of our control anyway.

Unfortunately, our app needs to connect to the Dropbox web service in order to receive back a token in the redirect uri so our app can retrieve resources stored in the user's Dropbox so connecting via Safari.app doesn't help. Would setting up a proxy between our app and the Dropbox server (in the customer's network) to capture the traffic help to illuminate for you what might be going on?

Thanks, Martin

Apologies, I thought you meant switching to Safari.app, e.g., using the Safari button in the bottom right of SFSafariViewController, during the flow did allow the user to connect your app (not just log in to Dropbox).

Anyway, at this point it's unclear what exactly the issue is, so I can't say for sure if inspecting the network traffic would help. For instance, if it's failing in JavaScript code, the network traffic may not reveal anything useful. 

That said, any information, or ideally a way to reproduce this, that you can share would be useful.