We’re excited to relaunch the Dropbox Replay community group! Learn more about Replay here.
Forum Widgets
Eternal "in_progress" in "check_job_status" ?
Hi there! After creating the file transfer task, I did not get a status other than "in_progress". I checked for 10 minutes, the result is the same. https://api.dropboxapi.com/2/files/save_url Headers: Dropbox-API-Path-Root:{".tag":"root","root":"***11017011"} Content-Type:application/json Body: { "path": "/TrueCare24/Getting started.pdf", "url": "https://cdn.filestackcontent.com/4HanfOIvSVW4gHeOUbm9" } Response: { ".tag": "async_job_id", "async_job_id": "SPaPOLIucOYAAAAAAAAAAQ" } https://api.dropboxapi.com/2/files/save_url/check_job_status Headers: Dropbox-API-Path-Root:{".tag":"root","root":"***11017011"} Content-Type:application/json Body: { "async_job_id": "SPaPOLIucOYAAAAAAAAAAQ" } Response: { ".tag": "in_progress" } There are no problems with other files. I have transferred many thousands of files and everything is ok. TrueCare24 is Team Folder
May timeouts when calling get_current_account endpoint
We’ve noticed a recent surge in errors reported by some users of our app when calling the get_current_account endpoint. Specifically, the requests are timing out, which is unusual because we haven't had any issues and our code has not changed. This issue started occurring last week and seems to be affecting users mainly in Canada. Could you help us understand if there are any known issues on Dropbox’s side, or if there have been recent changes to the API that could be causing these timeouts? Thanks in advance for your assistance! Regards, EnriqueThis app is not valid when trying to authenticate with Oauth
I'm trying to connect Salesforce to Dropbox and I've created an app on Dropbox. I've set up the Auth provider and have a URI redirect setup, but no matter if I use the actual URI, I always get the "This app is not valid" error message.I've verified the App key as the client id several times and it's correct, also verified all the scopes and all. All seems fine to me, can anybody please help me on this ?
Can't get Oauth to work... please help
Question or Issue I'm a little frustrated with the poor examples of dropbox... :-( I'm trying to start with Oauth, I'm trying to build a c# console app that will run for hours, since the tokens expire fast, I tried to get oauth integrated, but at step 1 it dies.. my code starts as follows: const string AppKey = "XXXXXXX"; // Replace with your App Key const string AppSecret = "XXXXXXX"; // Replace with your App Secret const string RedirectUri = "http://localhost:8080/"; // Replace with your Redirect URI // Generate a unique state for security string oauth2State = Guid.NewGuid().ToString("N"); // Get the authorization URI Uri authorizeUri = DropboxOAuth2Helper.GetAuthorizeUri( OAuthResponseType.Code, clientId: AppKey, new Uri(RedirectUri), state: oauth2State, tokenAccessType: TokenAccessType.Offline ); BUT as soon as my browser opens, I get an ugly error as follows: I did check the url and the client_id is there... (of course is not XXXXXXX) https://www.dropbox.com/oauth2/authorize?response_type=code&client_id=XXXXXXXXXX&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2F&state=65b4556d0f1f4639ac42b6cdfce08fb7&token_access_type=offline I understand my App Key is my client Id, thank you for any help you may bring.
Single API call creating duplicate file versions using Dropbox .Net Api
Hi Dropbox Support, I'm experiencing an issue with the Dropbox .NET API where a single file upload API call is creating two identical versions of the same file with the following problems: Problem details: Using Dropbox .NET API for file uploads One API request results in two file versions created 1ms apart Different attribution: One version shows "edited by user on web", the other shows "edited by user on API app" All uploads are done through API only - no web interface involvement This happens inconsistently - some files upload normally, others create duplicates API methods used: For small files: uploadArg = gcnew Dropbox::Api::Files::UploadArg(dropboxPath, Dropbox::Api::Files::WriteMode::Overwrite::Instance, false, clientModified, true, nullptr, false, nullptr); uploadTask = m_dropboxclient->Files->UploadAsync(uploadArg, fileStream); For large files: task = m_dropboxclient->Files->UploadSessionFinishAsync(cursor, commitInfo, nullptr, fileChunk);
Dropbox App created with one account, but seems to be identifying as a different account
I've created an app with a dedicated account that our administrator set up for me. The app works great. I've set up Salesforce to connect to the app using an Auth. Provider and Named Credentials. None of this has my name on it. The admin created a Team Folder that I want to be able to create sub folders under and then file requests for those sub folders. Whenever I create the sub folders, they were getting created under my account, not the system account and not the Team Folder. At first I was just using the /create/folder_v2 endpoint, but after going through a bunch of articles on it, I realized I probably needed to use the /sharing/share_folder endpoint. It still wasn't working quite right. Finally, I found this resource: https://developers.dropbox.com/dbx-team-files-guide Which suggested that I set the Dropbox-API-Path-Root in the header of the callout. So I got the root id from the api explorer from my service account and tried to use it, but I'm getting errors. And the errors HAVE MY NAME in it. Somehow it still is trying to create the folders under my named account instead of the account that was created by the app. Error creating folder: {"error":{".tag":"invalid_root","invalid_root":{".tag":"team","home_namespace_id":"xxxxxxxx","home_path":"/Barry ...","root_namespace_id":"xxxxxxxx"}},"error_summary":"invalid_root/"} Skipped file request due to folder creation error.
Dropbox Access Tokens - How do they work?
I'm currently using Dropbox Access Tokens which expire pretty quickly. I'm wanting to know when I publish my app, which downloads files from Dropbox, how I get a fully working Access Token that won't expire within a few hours. Do I need a membership of some sort for this to happen? I can't be updating access tokens at all as I need to be running a business. Cheers
