Stephen C.14 Dropboxer

Then I would recommend using Carthage, rather than CocoaPods, as it is less invasive. You can build the binaries with Carthage and then drage and drop them into each of your targets. This approach will work better, I think.

Can you try the steps here: https://stackoverflow.com/questions/30745675/cant-find-pods-modulemap-looking-in-wrong-directory

Strange. So am I. When I run `pod install` on the project you uploaded, and open the `xcworkspace` file, and build, it builds successfully. What's your output for `pod --version`? Mine is: ``` scobbe-mbp:server scobbe$ pod --version 1.2.0.beta.1 ```

Same project as the one you just uploaded (the second one). Which version of Xcode are you using? Please download the latest one, otherwise things might not compile.

This project builds fine for me after running `pod install` and opening the `.xcworkspace` file. Please ensure that you have Xcode Version 8.3.3+ installed.

I still get the pod warnings as well, but everything builds correctly for me. Please ensure that you close Xcode before calling `pod install` and that you open the `.xcworkspace` file and not the `.xcodeproj` file. Please also do a full a rebuild (cmd+option+shift+k) after `pod install`. If you have done all of these…

In your Podfile, please delete `use_frameworks!` for target `'SB'` only. Then things should work. (it doesn't really make sense to link a framework to a library).

Got it, thanks for letting me know. Yeah, we weren't crazy about dropping iOS 8 support on our end either, it's just that we needed access to `SFSafariViewController` (rather than `UIWebView`) for rendering our auth flow. Google, which offers our users a "Sign in With Google" option for logging in, has dropped support for…

Ah ok, yeah this still applies, even when the platform is iOS. As far as the crash, would you mind sharing the error message or stacktrace? Also, for my own curiosity's sake, at what point do you think you will consider dropping support for iOS 8 (which now constitutes < 3% of all iOS users)?

If you uncomment `target 'SB' do` in your Podfile, and then you run `pod install`, even with the CocoaPods errors, the .xcworkspace file builds for me for target `SB`. Can you confirm this?

Sorry for the confusion here. You should not be using the one that Carthage builds, but instead the one that is built by your subproject (I think it's the only one you'll have access to when you do the following steps): In the Project Navigator in Xcode, select your project, and then navigate to your project's build target…

Sorry for the delay here. Not sure why CocoaPods isn't working. Try adding `Pods_BASIC.framework` to `Link Binary With Libraries` under `Build Phases` for `SB` target (see attached image). Let me know if this works for you.

Try -downloadUrl:rev:overwrite:destination:.

Hi Nguyen, Unfortunately, there is no way to facillitate the authentication flow from a share extension, which is not a "standalone" app, and therefore has no way of handling the auth redirect. Sorry, I wish I could be more helpful!

If you're integrating with Dropbox with a mobile app or a desktop app, you don't need to do add an explicit url here. What you do need to do is to register your app at the OS level to handle a particular url scheme (db-<YOUR APP KEY>), which will handle the auth redirect. If you're integrating with Dropbox with a web app,…

Dropbox unfortunately doesn't distinguish between write and update. If any part of a file has changed, no matter how small, the entire file is re-uploaded. What `isUpdate` allows you to do is manage the case where *nothing* has changed in the file, in which case, no upload is performed. You do this by getting the metadata…

Go to https://www.dropbox.com/developers/apps, select your app, and then you will find a box where you can add a redirect uri.

Unfortunately, a configurable max file size is not available at this point, but we are tracking this feature request. Sorry I can't be more helpful.

You're correct, Dropbox iOS app only supports iOS 9, so yes, anyone not running iOS 9 will not be able to use Dropbox. But it's important to consider that this is an increasingly diminishing fraction of users. Less than 3% of users are on iOS 8 and less than 2% are on all other versions of iOS according to Apple.

Ah, I see. If you have been using the `getAccessToken()` method for access tokens, then you do not need to perform a token migration, as you are already using OAuth 2.0 tokens, which work for both API v1 and API v2. Is this the case for you?

I checked our performance graphs, and it doesn't appear that any of our upload endpoints have higher latency than normal. Of course, double check your connection and make sure it's robust. If this issue persists for more than a few hours and if you notice it consistently, re-ping this thread, and I can take a closer look.

Hi Mark, sorry for the delay here. Unfortunately, the SDK doesn't expose an interface for implementing this session re-attachment behavior. I'm no expert in this behavior, but if I recall, after sesion reattachment, you need to resupply a response handler to handle the upload or download that completed while your app was…

Yeah it's not ideal, but this is the sort of the price of "batching" everything at once. Because we don't make so many trips to where our metadata lives during upload, you can upload a lot of stuff at once without running into rate-limiting. But because you do these metadata write operations all at once as the final step,…

Are you still seeing this issue? Would you mind sharing some sample code?

This is absolutely on our radar, and we are trying to prioritize it in light of the API v1 deprecation timeline. Will update the thread again when we make this fix.

Thanks for reaching out. Unfortunately, we have no plans to add `client_modified` to your folder metadata result, as it would require a rather substantial change to our filesystem infrastructure. For API v1, the modified time of a folder is actually quite misleading. It reflects only when the folder was created and/or if…

Sorry for the confusion here. I updated the README to make it clearer that the ouput path is the full path, including file name. Let us know if you have any other questions or feedback for the SDK.

Unfortunately, Dropbox currently doesn't offer a way to track API calls based on whether they target API v1 or API v2. I would recommend tracking API v2 adoption based on your own analytics (or the analytics of whichever service you're using to distribute your app). Specifically, I would look at the number of downloads of…

It looks like you are receiving the API v1 deprecation warning because you have not yet acknowledged the API v1 deprecation. Please login to Dropbox and go to https://www.dropbox.com/developers, and the click the acknowledge button on the big yellow banner that appears. Then, this warning will go away. Please let me know…

Thanks for reaching out. I would recommend taking a look at the DbxOAuth1Upgrader class, which allows you to migrate OAuth 1.0 tokens to OAuth 2.0 tokens. In OAuth 2.0, there is no access token secret, only an access token. Please let me know if you have additional questions. Thank you!