Dropbox custom URL scheme

Здравко To clarify, that is meant for the implementation in the official Dropbox SDK(s), and third parties can certainly use the official Dropbox SDKs, but third parties are not meant to re-implement the functionality using /1/connect themselves.

Ah ok I am using the api itself not the dropbox sdk. I should have clarified that. Sorry about the confusion. I am a novice at this. Here is a screenshot of what happens before i push the accept button: 

After I push the button it greys out the accept button:

Thank you for all your help!

Doesn't matter whether you use SDK or not. Your screenshots just show that for some reason your schema is not able to activate any installed handler (including, but not only your application). Unfortunately, your screenshots don't carry too much information for details. In general different reasons can be, but may be set in 2 groups. First, your application may not be installed correctly as particular scheme handler. This is easier to check. Just put in your browser address line a URI that matches your application expectations (including the scheme). Does, after hitting enter key, your application get up in front of the browser? If Yes, the check is passed successfully, but if no you have some configuration mistake in the application and have to fix it. Second, redirect URI that comes from Dropbox after confirmation may not match to your idea. To see what comes there, an easy way is to copy your browser address line before hitting 'Allow' and paste in desktop browser address line. Usually there are tools letting you trace what's going on. In network tab you can see the redirect request (code 302,after hitting Allow) and find out What's in the 'location' response header. Does it match your (application') expectations, including schema? If Yes, it's Ok, but if no, you have mistake in URL, related to launching the linking process, construction (more careful focusing on the details may be needed).

Hope this gives direction.

So it fails the first check. Here are the guides i have been trying to follow: 

https://docs.expo.dev/guides/linking/#linking-to-your-app 

https://docs.expo.dev/guides/linking/

According to the documentation all I need is to put a scheme in the app.json file which I have done: 

}

Then I use this in my authtnetication script: 

Here is how I build my redirect URI:

---

squidlauncher64 wrote:

So it fails the first check. ...

---

In such case your application cannot be launched and that's why your browser "freezes". At that moment the browser does exactly what you did - tries open the same URI - unsuccessfully. To be honest, I'm not familiar with your environment and cannot say what exactly is wrong or if is what you say enough. The only fact is that, as seems (according your words), the application is NOT registered as a handler properly. You have to check and fix whatever needed. The only thing I would advise is to check if all parameters are available in end package (for example, in Android manifest have to be registered an activity with appropriate intent filter, that matches your scheme). That would be a good start point, for instance. 😉

Good luck.