Greg-DB Dropbox Community Moderator

Thanks! I was able to reproduce the issue by removing the value for CFBundleIdentifier. Yours is $(PRODUCT_BUNDLE_IDENTIFIER), so make sure that "Product Bundle Identifier" is set in your target's Build Settings. That's listed in the Packaging section.

I don't see in your code where you're attempting the search call. Can you share that part? Thanks!

Thanks! The expected result here is that the dialog would show the app name, and clicking "Allow" would send the user back to the app. Can you share your plist file? That controls how your app is registered for this. In particular, for the null app name issue, I think CFBundleIdentifier may be relevant.

The endpoints for adding templates aren't currently exposed, as the feature is still in development. I'll send this along as a request for them though.

Since you're using Swift, are you using the official SwiftyDropbox SDK? In that case, you'd use the search method in FilesRoutes. As long as the call succeeds, it will return a SearchResult. You can then use the SearchResult.matches, which is an array of SearchMatch. SearchMatch.metadata contains the FileMetadata for the…

I'm not sure off hand what may be causing this. Can you share a screenshot showing this so I can make sure I understand exactly what you're seeing and try to reproduce it? Thanks in advance!

It looks like you opened a new thread for this, so I'll take a look and reply there: https://www.dropboxforum.com/t5/API-support/Dropbox-api-v2-null-Do-you-want-to-allow-this-page-to-open-null/m-p/201802#M9540

Using the Dropbox API, you can search for files and folders under a particular path using the /2/files/search endpoint: https://www.dropbox.com/developers/documentation/http/documentation#files-search If you're using an official SDK, there will be a corresponding search method for that.

That's the OAuth 2 "token" flow, where the access token is returned on the redirect URI fragment. That's meant more for client-side apps. For server-side apps, you should use the "code" flow. You can find more information here: https://www.dropbox.com/developers/documentation/http/documentation#authorization

Thanks for the report! We're looking into it.

The app authorization flow redirect is directed by the db-<APP_KEY> URL scheme registered in an app's plist file, in the CFBundleURLTypes section. It sounds like you have the same app key registered in both DBMacApp and ezReceiptMac, causing the undesired redirect. Since DBMacApp was just for testing, the easiest solution…

We're able to reproduce the issue, so we shouldn't need any more information from your side. Thanks though!

This is a bug with the library itself, and not something you should have to handle yourself. We're looking into it, but I don't have a timeline for a fix right now.

Thanks! By the way, for reference, the path is also localized for accounts in other languages, and users can move and rename app folders whenever they want.

No, the Dropbox API doesn't expose a way for apps with the app folder app to query their full app folder path. The API is designed such that apps shouldn't need to know their own app folder path though. I.e., when such an app references a path using the API, the API automatically translates the root to be the app folder…

[Cross-linking for reference: https://stackoverflow.com/questions/41592694/how-to-get-upload-progress-with-java-sdk-for-dropbox-api-v2] The API v2 Java SDK doesn't currently expose progress listeners for uploads, but I'll be sure to pass this along as a feature request. 

The API doesn't offer a way to do that, but I'll be sure to pass this along as a feature request. I can't promise if or when that may be implemented though.

Thanks for the detailed report! We're looking into it.

I'm not familiar enough with the Xcode build system to say confidently what the issue may be, but there's a post here about an issue that sounds like this: https://stackoverflow.com/questions/39588223/xcode-8-recompiling-complete-code-everytime I'll ask the team to review this though.

I just wrote this for this thread, but I'll make a note to post it on StackOverflow later. Thanks!

You don't need to use DbxRawClientV2. You should instead use DbxClientV2, as shown in the examples, e.g., here. Calling addFileMember would look like this: DbxRequestConfig config = new DbxRequestConfig("example"); DbxClientV2 client = new DbxClientV2(config, ACCESS_TOKEN); List<MemberSelector> newMembers = new…

Thanks! I can't seem to reproduce that issue though. This works correctly for me: $.ajax({ url: 'https://api.dropboxapi.com/2/files/get_metadata', type: 'POST', processData: false, data: JSON.stringify({"path": "/Recipes"}), contentType: 'application/json', headers: { "Authorization": "Bearer <APP FOLDER ACCESS TOKEN>" },…

I don't have an ETA for a fix right now. I'll post here once I have an update.

You mentioned your app has an app folder, so can you double check that the app folder itself contains a "Recipes" folder in it? I.e., when you look at dropbox.com, that would be at /Apps/<app folder name/Recipes. Also, if you've registered multiple apps or used multiple accounts, make sure you're using an access token for…

Is the get_file_and_metadata call running successfully? It sounds like that error message is coming from your Firebase database method, so I'm afraid I can't be of much help here. You may want to refer to the documentation/support channels for that instead. Also, note that you're using Dropbox API v1, which is deprecated.…

That's correct.

Thanks for the report attic! That's the same issue as the one volkeru reported. We're working on it.

Thanks for the feedback!

[Cross-linking for reference: https://stackoverflow.com/questions/41537788/how-to-use-proxies-with-dropbox-api ] You should be able to create a requests session with proxies using dropbox.create_session and pass that to dropbox.Dropbox as the session parameter. [MODERATOR NOTE: BROKEN LINKS WERE REMOVED]

The simplest solution is to upload files serially, but alternatively, we do have a data ingress guide here that covers this issue and details how you can avoid this issue by committing files in batches: https://www.dropbox.com/developers/reference/data-ingress-guide Hope this helps!