Greg-DB Dropbox Community Moderator

Great! I'm glad to hear you tracked this down. I'll ask the team to see if we can make this fail more noisily in that case.

Apologies, TestData.fileData should indeed just be fileData (per the first line in the example). Also, the path parameter should be the full path in the Dropbox account where you want to upload the file, including the desired file extension. So, for example, instead of "/test/path/in/Dropbox/account", if you wanted to…

To upload a file using the API, you can use the /2/files/upload endpoint: https://www.dropbox.com/developers/documentation/http/documentation#files-upload That is a "Content-upload" style endpoint, so it expects the file contents in the request body, as documented in the "Request and response formats" section:…

As a matter of security OAuth 2 redirect URIs are required to use https:// not http://. Likewise, also as a security feature, OAuth2 redirect URIs must be pre-registered exactly. One thing you may be able to do instead is to use one static redirect URI but encode the necessary information in the 'state' parameter, and…

Unfortunately I don't have any specific metrics to share, nor is there a good value I can recommend. This delay will vary by account, and even over time for the same account, as it depends on how much file activity there is in the account. You may want to try a few values to see what works well for the users of your app in…

Can you share the code you have so far and post the error or unexpected output you're getting? If I see what's not working for you, I may be able to offer more help. Also, is your access token just one piece like that? If so, you likely have an OAuth 2 access token. You indicated you're using the v1 iOS Core SDK, which…

Hi Steve, no, unfortunately the SDK doesn't offer anything analogous to status.anyInProgress, but I'll be sure to pass this along as a feature request. You'll need to keep track of this state via your app's logic instead. (I.e., set some state when kicking off the operation, and unset it when the response block runs.)

Based on the Cartfile documentation, it looks like the operator for that is "==", so you'd need "== 3.0.11".

All Dropbox API calls require TLS, so everything is encrypted in transit. We also always recommend that users use device encryption, so that any copies of files stored on their local devices would be encrypted too. You can find more information about the security of Dropbox systems themselves at the following links:…

You don't have to share your code if you don't want to, but for what it's worth, we won't judge your code! :-) If the view controller setup seems unlikely to be the problem, perhaps it's something to do with the UIApplication? Is there anything unusual about your [UIApplication sharedApplication] in that app? In any case,…

Thanks! If it is due to an unusual view controller setup it's unlikely we'll be able to help without seeing more code. Would you be able to share the relevant code, and send us a build we can try? You can write in privately here if you'd prefer: https://www.dropbox.com/developers/contact

Thanks for pointing out the old examples! We'll get that fixed up in the documentation. And thanks for the rest of the feedback on the documentation! It's much appreciated. Anyway, regarding the issue of authorizeFromController not working, since it's working in your other app and the sample app, it seems like the issue…

Yes, unfortunately we had to drop support for iOS 8. (This is because we are moving to Safari View Controller, in order to better support the Google Sign In flow, which no longer allows web views: https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html , among other features.) You can…

Oh, apologies, I didn't realize the second part was still Carthage output. Yes, in that case, please try removing the entire Carthage build of the SDK in that app and re-installing it.

There have been some breaking changes to the SDK over the various updates. (The SDKs mostly use Semantic Versioning to indicate breaking changes/feature updates/bug fixes.) If you're updating from an old version, you'll need to update your code for those changes. You can find more information in the release log.

1) There isn't any way to enable additional output. It should already be yielding errors/output if something isn't working. 2) If you prefer, you can configure your Cartfile like this to always take the latest version: # ObjectiveDropboxOfficial github "https://github.com/dropbox/dropbox-sdk-obj-c" The Cartfile…

Yes, the official Dropbox app is still expected to be used in that case. The browserAuth parameter only controls what happens if the official app isn't installed. It determines whether or not to use the external browser in that case. Anyway, the copy of the SDK you have checked out appears to be a bit old. You can update…

You should only encode your redirect URI ( http://localhost/soft/softaculous/enduser/index.live.php ) since it's being provided as a URL parameter, and not the /authorize URL itself where you send the user to authorize your app. A 405 error should indicate that you're using the wrong HTTP method. The /oauth2/token endpoint…

Thanks for letting me know. We'll look into it.

Thanks! In that case, comparing against your other app or the DBRoulette sample app would be a good place for begin troubleshooting this, since you're not getting any error or output. The DBRoulette sample app does use the sample authorization flow. It's available as three versions, one for each of the supported…

Hi Bob, since this was previously working for you, can you check your version control repository to see what may have changed here in your code? Or, did this stop working when you updated the version of the Dropbox SDK you're using? In either case, is your "VC" parameter your view controller instance? Normally that's just…

Thanks! That may have just been a transient issue on our side. Can you try once more now? Please share the X-Dropbox-Request-Id again if you still get a 500.

You can cast that error as NSError to access the specific parts of the error information, such as: case .clientError(let clientError as NSError): print("ClientError code: \(clientError.code)") print("ClientError domain: \(clientError.domain)")

Can you include the full request and response for that? Please do include the response headers so we can look into it.

Thanks for the post! This is expected, media information won't be returned for all media types. With API v2, you should use the file extension in place of the mime type. I'll be sure to pass this along as feedback though.

I suspect the issue is that you're missing the "Content-Type" header. It should be "Content-Type: application/x-www-form-urlencoded". Try that and let me know if it doesn't help.

It looks like you have an extra redirect in the flow you have implemented. Specifically, you shouldn't be doing step 3. You should only direct the user to /oauth2/authorize once. It appears your app is directing them again a second time, including the extra 'code' parameter the second time. This blog post may be helpful:…

Once you've set the access token in the session, and retrieved a client with that session, as above, you can use that client to make calls. The tutorial covers the basic of using a client to make calls. For example, to list a folder: https://www.dropbox.com/developers-v1/core/start/ios#listing What part specifically isn't…

Can you elaborate on what information for the root folder you're using from API v1? API v2 doesn't support the root folder on /2/files/get_metadata. If you need to list the contents of the root folder, you should call /2/files/list_folder[/continue] with "" as the path:…

Thanks for following up. In that case, returning an HTML success page like that is the best solution. Note that we don't recommend using an embedded web view, as the Google Sign In flow won't work with that in the future: https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html