Greg-DB Dropbox Community Moderator

We're looking into this, and for reference, we are still now returning a "Content-Type" of "audio/mp4" for .m4a files, and I can confirm we are currently returning "application/octet-stream" for .m4b files. From what we can tell though, we did not previously return a more specific "Content-Type" like "audio/mp4" for .m4b.…

[Cross-linking for reference: https://github.com/dropbox/SwiftyDropbox/issues/345 ] @"muthulingam" Thanks for the report. I just tried reproducing this with the same version of the Dropbox SwiftyDropbox SDK and Dropbox app, but it worked successfully for me. My test device is on iOS 15.0.2 though, so it may be worth…

Thanks for checking that! We'll look into it.

Thanks for the report. Can you try switching to files_search_v2/files_search_continue_v2 and let me know if you do or don't see the issue with that as well?

Please reach out to your partner contact at Dropbox (i.e., whoever you worked with to get your app listed originally) for help with this. If you are unable to reach them, then open a ticket here instead.

I don't have an update on this yet. I'll check in with the team and follow up here once I have any news.

@"Kris Brown" You can fill out this form to request a Dropbox Business Development Account, which should use the old configuration by default.

The Dropbox API does now have two different types of access tokens: "long-lived" and "short-lived". Long-lived access tokens don't expire by default, while short-lived access tokens expire after a short period of time (with an option to use "refresh tokens" for long-term access). Dropbox is moving to exclusively issuing…

Thanks for the report! Can you also share: * the code you're using to start the authorization flow * whether or not you also have the non-scenes "Handle redirect back into SDK" code added * the version number of the Dropbox SDK * the version number of the Dropbox iOS app * the version number of iOS

1. Thanks, we'll check on this. 2. The "Maximum response size reached" error doesn't appear to be coming from Dropbox itself. I also just tried and I was able to successfully access a file larger than 100 MB via a temporary link retrieved by get_temporary_link, so it looks like this is a client-side issue. You'll need to…

Update: to help accommodate clients with this issue who can't apply a fix client-side, we're no longer returning the "#" at the end of these links.

Update: we're no longer returning the "#" at the end of these links.

The Dropbox API doesn't offer the ability to programmatically set the connected account's user name, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. For reference, the Dropbox Business API does offer the ability to set a team member's name via the…

@"Ingi" @"flygecko" Thanks for following up. It looks like we're planning on removing the "#" on our side to help accommodate this. I'll follow up here if/when that is done. @"flygecko" I'm not sure I follow your question regarding the access token. Note that migrating your app to scopes and/or creating a new access token…

The behavior of putting back the unshared folder in your home folder instead of the original location does not sound expected. Would you be able to share a sample of the API requests/responses showing a case of this so we can look into it specifically? (Be sure to redact your access token though.) Feel free to open an API…

Thanks for following up. I see you're referring to the links returned by the /2/files/get_temporary_link endpoint. Per the Dropbox API spec, the returned GetTemporaryLinkResult.link field is only documented as String without a more specific format/domain guaranteed. The exact link format/domain used may vary over time as…

[Cross-linking for reference: https://github.com/dropbox/dropbox-sdk-java/issues/353 ] Thanks for following up. I'm glad to hear you already got this working. For reference, you can find more information on how the user limit works here.

@"ivanrinaldo" No, unfortunately I don't have an update on this request.

That's correct. This is because some scopes depend on others. When you see a scope checked but greyed out, like in the screencast you shared, that means that that scope is enabled, and can't be disabled because another scope that depends on it is also enabled. For example, 'files.metadata.write' and 'files.content.write'…

Thanks for following up. I'm glad to hear you tracked this down. The "#" is a character for identifying the beginning of the "fragment" portion in a URI. It's a valid part of a URL, but it sounds like your HTTPS client isn't handling it properly. It's not strictly needed in this case though so you can remove it in your…

Thanks for following up with the additional information. For reference, there are a few different types of sharing on Dropbox, and it sounds like you're referring to the type of individual file sharing where the recipient can access the shared file on the Dropbox web site, e.g., at https://www.dropbox.com/share/recents ,…

Thanks for sharing your solution! We don't have any sample code for Xamarin unfortunately.

Yes, if the app is disconnected (also sometimes called "unlinked"), that will revoke the access token(s), and using any such access token will result in that error.

An 'invalid_access_token' error like this should indicate that the access token the client is providing (in the "Authorization" header) is not valid. For instance, it is not an actual access token string, or the access token was revoked. Are you using a valid access token? I recommend reading the OAuth Guide and Error…

Can you share the rest of the steps/code to reproduce the error you're getting? Specifically, you shared the code to retrieving the link itself, but how are you accessing the link that then fails? I can use the code you shared to retrieve a temporary link, and accessing that link is working successfully for me. Is there…

It looks like your client is getting a 400, but I just gave that a link a try and it is working for me. Can you print out the full request and response, including both headers and bodies, to see what might be going on there?

This error message is referring to specifying what account on the Business team to operate on behalf of. For reference, when using any "team scopes", the resulting access token is connected to an entire Dropbox Business team, not an individual account. So, when using a team-scoped access token to access user-specific…

The redirect URIs only apply to the OAuth flow. Since you're processing an actual API call here, not the OAuth flow, that wouldn't be relevant. What's the full error message in this case? With the JavaScript SDK you're using, try `console.log(error.error);`.

No, the API doesn't offer anything else quite like that. You'll need to retrieve all of the results and apply whatever sorting you want client-side.

These endpoints don't offer a way to have subfolders listed first, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.