RTS S. Helpful | Level 7

Thanks, I used the Code flow as it looked more secure. It would seem that custom URL schemes would be as secure as LOCALHOST ... both of which can only work on the user's device.

The image did not get attached ... here it is as a link: Screen Capture

static let CLIENT_ID = "......" static let CLIENT_SECRET = "...." static let REDIRECT_URL = "myapp://Auth" static let OAUTH_URL = "https://www.dropbox.com/1/oauth2/authorize" override func OAuthURL() -> String { return String(format:"%@?redirect_uri=%@&response_type=code&client_id=%@&force_reapprove=true",…

Could you post the answer here ... I am having a similar problem. I have not needed to login in long time ... (using a saved token) ... moved to a new tablet and having a problem. I successfully use the OAuth flow with Google Drive and OneDrive. I am not sure if this has something to do with:…

Thank you ... I have everything I need. As I indicated it would still be a nice feature to be able to access to a publicly shared folder/file without the need to authenticate any user. If I have the shared URL as an end user I can use a browser to navigate the folder and download a publicly shared folder ... I do not need…

I use the same code to Navigate (files/list_folder) and download (files/download) for both my APP/User token and for a shared folder using a User token. I am able to download a file using an id:xxxx for the path using my APP/User token. But having problems with the shared folder: The following is for a Test File in a Test…

I can traverse the folder Shared Folder using a USER token (as opposed to a App/User token) using the files/list endpoint. The path is relative to this shared folder. Do I use a path of the form {id:UniqueID} ? with the files/download request ? Or do I somehow have to use the {sharing_info: ???? } property ? If it's the…

A comment ... the interface is a little strange ... I get an OutputStream that I must write to for uploading the initial chunk. I must supply an InputStream that the API reads from for the middle and last chunks.

Thank you ... I can work from this ... it was not obvious how you to get the session ID.

I have already added this .. to solve my problem ... but why is it marked provided ? Your software has a dependency on it. Provided is typically for things that are provided by the run time environment like JDK or things that may need a license. Your install notes should state that this needs to be installed, and/or this…

It took me one day to do the Auth.swift DropBoxConnectController ... which is a View controller to display the Web View user interface ... and only because I never used that class before and was having problems in Swift with it ... So I implemented it in Objective C. The Alamofire already supports OSX. About 15 minutes to…

I previously asked about connecting to multiple Accounts in the context of OSX and was told that it would be supported for API V2. Now I understand that there is no API V2 support for OSX. This is very disappointing.

Yep, my upload (with an input stream) and Session upload with chunks of NSData worked after settings the WriteMode (In the latter case the upload always worked, it was the finishing the session and saving the filed that failed) The error messages are terrible and I would have never guessed from the error what the problem…

Some more problems with uploads (Version 1.0) ... let ins = NSInputStream(fileAtPath: fromPath) client.files.upload(path:"/AccountInfo.json", ins!) I also get the following response error: Printing description of errorType: (SwiftyDropbox.CallError<SwiftyDropbox.Files.UploadError>?) errorType = RouteError { RouteError = {…

I upgraded to API Version 1.0 Here is the debugger output of the input variables before calling filesUploadSessionFinish and after getting the response: Printing description of cursor: { offset = 82995; "session_id" = AAAAAAAAEHSrFUSNImgWDg; } Printing description of info: { autorename = 0; mode = { ".tag" = add; }; mute =…

Oops ... I meant that the filesUploadSessionFinish failed. In two cases ... the one I just reported on was with an empty NSDATA() as the body. Previously I also had a problem when I passed and NSDATA object with data ... It failed with a different error. The dbPath was /AccountInfo.json ... logged in as my APP context.…

Is there a reason why filesUploadSessionAppend takes an offset and Session ID and filesUploadSessionFinish takes a Files.UploadSessionCursor which wraps the Offset and Session ID ? Seems like these calls should hava a similar calling convention except that SessionFinsish should have the extra CommitInfo Actually I think…

If I try to load a 1GB files with a Stream input using filesUploadSessionStart will the file get completely uploaded by the time it calls the response ? If not how do I find how much was transferred so I know where to start with subsequent filesUploadSessionAppend ... that's the part I am missing.

I downloaded a couple of days ago using Cocoa Pods with tag '0.7'

That solved the access problem. Does not make any sense to me ... There is still an error handling problem which causes a fatal exit.

I also get the error when I try to call filesListFolder with a path of "/"

OK, but I hope this is stable for V3 .... user identification is critical for resource not maintained entirely on your server.

My app has been around since before V2 ... I already have UID in the database. I have already converted OSX, IOS to V2, developed the .NET APP. All of those have access to UID. Now you are recommending that I stay on V1 for android ? Is this a long term stable identifier ?

Is there a way to get UID in Java API ? I have been using the UID as a user identifier in my APP ... I have been able to access this in Swify and .NET

Steve, My wrapper is very specific to my APP. So I do not think it would be applicable as a general API. My wrapper handles all of the errors. It's a simple object that references the Client Object and has a bunch of methods to manipulate the DB Files API. They typically return nil for error or the primary subject of the…

I think it's unlikely that this will change soon ... Swifty is bootstrapped from Alamofire which is also a Swift base framework However Alamofire is derived from an Open Source Objective-C library. In general I like the style of the new interface ... passing blocks/closures for the completion of a request as opposed to the…

If this comes in phases .. it would be good to get the Files.Metadata classes available in Objective-C. I find it convenient to keep meta associated with a Dropbox path in my App. I need to handle all the various Files.Metadata sub classes. The Users.Account class would also be useful, but sine any app only has one to a…