Child Item

.Net Maui

Hi, I need to find a way to connect my app with Dropbox. I am moving from a Xamarin.iOS app to .net Maui due to Xamarin not being supported anymore. (I can't just change my app to the new .NET as the libraries I used were not ported)

Everything I find onlines shows doing this with a webview, but that is no longer allowed.

I really need to find a way to make this work with .Net Maui, surely this is possible?

Find more posts tagged with

API

Abuse

Comments

Greg-DB

We can't provide help for the third party platforms as they're not made by Dropbox, but please let me know if there's something we can help with on the Dropbox API or SDK itself. Perhaps someone else here has some experience with Maui though.

As for the Dropbox .NET SDK, you can find the information that here. That should support .NET Standard 2.0. You can find the examples for the SDK here.

phunction

The main issue is the call back to the platform and adding some kind of listener.

I found somewhere a way to bring up a web login, and they could manually copy the key that is presented so it could be pasted into my app. I can't remember where that was and if it provided a refresh token as well so they would not have to do that every time the app is launched.

Or if someone else has an idea on how to make it work without that.

Is there a way to allow a login without having to spawn an external browser?

Здравко

@phunction wrote:
...
I found somewhere a way to bring up a web login, and they could manually copy the key that is presented so it could be pasted into my app. ...

Hi @phunction,

If I have to bet, you have noticed usage of ProcessCodeFlowAsync method which first parameter accepts authentication code receive from browser. ...

@phunction wrote:
... and if it provided a refresh token ...

That depends on whether you have set tokenAccessType during URL construction to Offline or no. In general it's supported.

Good luck.

Greg-DB

@phunction Здравко is correct, you can use ProcessCodeFlowAsync to complete the authorization flow by having the user copy/paste the authorization code into the app, passing the authorization code to that 'code' parameter.

You do need to send the user through the authorization flow in their system browser, but when you don't use a redirect URI in the authorization flow, that authorization code is presented directly to the user directly so they can copy/paste it. That way you can still implement the flow even if you can't redirect to some listener.

And yes, to get a refresh token, you'll need to request "offline" access.