Child Item

Xcode swiftydropbox setup

Hey,

Has anyone been able to set up Swiftydropbox without any user prompt ? I dont know the order or what needs to be called. I don't want the user to have to set up any login. Any quick breakdowns on the process for me to use a refresh key and app key in order to get the access token without a user prompt would be amazing

Thank you !

Find more posts tagged with

Comments

Greg-DB

It's not possible to skip the app authorization flow and gain access to the end-user's account. In order for the app to access the user's account, the user needs to grant the app access to their account. This only needs to be done manually once per app-account pair.

whats

I dont want to gain access to their account, I want to use my account refresh token and app key. Is this possible ?

Greg-DB

The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. While it is technically possible to always connect to just one account for all users, we do not officially support this, for various technical and security reasons.

whats

Absolutely understandable, would you be able to direct me on this flow?

Здравко

@whats, you can take a look here how you can perform OAuth by hands and use the refresh token in your code (you'll need app secret too by the way).

whats

Hey thank you so much! What does your code look like in xcode once you have these parameters? What are you calling?

Здравко

@whats wrote:
... What does your code look like in xcode once you have these parameters? What are you calling?

The code anywhere looks exactly like you would code it, nothing else. There is no a single way to do it - it's matter of design decision. If you want to stick as much as possible to the Dropbox Swift SDK, you should use PKCE version of what I posted (i.e. not exactly the same) - Dropbox Swift SDK doesn't support app secret. In such a case (PKCE usage) you need to implement DropboxAccessToken object yourself and pass it further on client object initialization.

To avoid PKCE you need to re-implement (replace) refreshing process (adding app secret there).

Good luck.

whats

Hey @Здравко ! I tried building this today and had a few questions if you're know the answers,

-When you say "replace" the refreshing process, what do you mean exactly?
-Where would I use the app secret? Would this only be in the beta 10.0.1?
-Do I use the DropboxTransportClient?
-Is the initial call, dropbox = DropboxClient(key,secret,refreshtoken)? Then use dropbox to call api?

Thank you for all the help !

Здравко

@whats wrote:
...
-When you say "replace" the refreshing process, what do you mean exactly?
...

😁 Yeah... Maybe I said it too.. "hard". That's why I clarified: "adding app secret". "replace" here means edit the algorithm, no so much actual replace. This results from, as I already said, application secret is NOT supported in Dropbox Swift SDK (don't ask me why). It's supported by API itself (as you probably already know) and most of the other Dropbox SDKs.

@whats wrote:
...
-Where would I use the app secret? Would this only be in the beta 10.0.1?
...

No, it's not related to any particular version, but rather all of them (or that what you're using).

@whats wrote:
...
-Do I use the DropboxTransportClient?
...

Hm..🤔 To be honest, I'm not sure what you mean here. You will always use that class, but you don't need to do it explicitly. It's just a internal class. If needed, clarify what you mean.

@whats wrote:
...
-Is the initial call, dropbox = DropboxClient(key,secret,refreshtoken)? Then use dropbox to call api?
...

🙂 As far as I know there is no such an init call (might be convenient for many users, but...). The refresh token itself is part of the DropboxAccessToken that you need to pass (you don't need to handle/pass it in addition). App key is part of the app configuration (doesn't need to pass the refresh token in addition). You can add app secret to the configuration in the same way as done already for the app key and use it further in the updated refreshing (again in the same way as app key is used there - the only change needed there).

whats

Thank you again for the detailed reply! I guess I am lost to which part needs the app secret, I was unable to locate where I could pass it

Здравко

@whats, If it's so hard for you to add support for app secret, then perform OAuth flow using PKCE (as I mentioned it as a variant before). In such a way you wouldn't need app secret and can use Dropbox Swift SDK as is (without change). You don't need to implement such a flow in the same language. Throughout the forum and other SDKs are lot of examples you can "hire". For instance take a look here. It's a Python script that you can perform OAuth on (it uses PKCE). Once you authenticate yourself, get the saved refresh token and use it. 😉 In such a case only app key would be needed - something Dropbox Swift SDK supports. That's it.

Hope this helps.

PS: Keep in mind that providing this application to somebody else will let other person access to your account - something potentially dangerous for your data - take care.

whats

I have performed the Oauth and have the refresh key, my implementation currently isnt working. I assume its an authentication issue, is there any way to have the http request errors post to console when testing the app so that I can see what error I am running into?

Greg-DB

@whats The SwiftyDropbox SDK doesn't offer a way to print out the raw HTTP request/response, but you should be able to check the `error` for any given call, e.g., as shown in the `response` handler in the examples here.

whats

Hey @Здравко would this be the right approach? I would then call client.upload for a rough example. I have the manually obtained refreshToken and appKey

class <CLASSNAME>: TransportClient{

private var client:DropboxClient

init(){

client=DropboxClient(appKey:"<APPKEY>",refreshToken:"<REFRESHTOKEN>")

}

extension DropboxClient{

public convenience init(appKey:"<APPKEY>",refreshToken:"<REFRESHTOKEN>"){

let transportClient=DropboxTransportClientImpl(transportClient:transportClient:)

self.init(transportClient:transportClient)

}

extension DropboxTransportClientImpl{

public convenience init(appKey:"<APPKEY>",refreshToken:"<REFRESHTOKEN>"){

let oauthManager=DropboxOAuthManager(appKey:"<APPKEY>",secureStorageAccess: SecureStorageAccesDefaultImpl.init())

var dropboxToken=DropboxAccessToken(accessToken:"",uid:"",refreshToken:"<REFRESHTOKEN>")

oauthManager.refreshAccessToken(dropboxToken,scopes:[],queue:nil,completion:{_in})

let accessTokenProvider=ShortLivedAccessTokenProvider(token:dropboxToken,tokenRefresher:oauthManager)

self.init(accessTokenProvider:accessTokenProvider,selectUser:nil,pathRoot:nil)

}

Здравко

Hm..🤔 Once you have refresh token using PKCE (you didn't mention but I suppose you used PKCE since it's mandatory for skipping app secret), would be easier just to call something like:

import SwiftyDropbox

let token = DropboxAccessToken(accessToken: "", uid: "",
                               refreshToken: "<your refresh token here>",
                               tokenExpirationTimestamp: ("0" as TimeInterval))
let client = DropboxClient(accessToken: token,
                   dropboxOauthManager: DropboxOAuthManager.sharedOAuthManager)

... and use the client further on as in all examples. It's simpler. Isn't it? 🧐 The above code is just an illustration. You should have initialized the SDK already before running above code - see again the referred example (where the app key goes)!

PS: While you use PKCE, you don't need to change anything in SDK itself. 😉

whats

Hmmm, I tried to implement these three things and seem to have made it worse. It now crashes as soon as it launches with the Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction:4

Здравко

This means that your (Intel) processor tries access something uninitialized (most probably). Did you initialize your SDK in advance, as I noted? If not, DropboxOAuthManager.sharedOAuthManager points to nowhere! Something that likely be reason for such signal.

Of course might be something else too. You can investigate where this happens. 🙋 Try debug it!

whats

Interesting! Thank you for all the help so far, I was thinking that I perhaps didnt play the initialization in the correct spot. I will investigate this further !