Framework needs to be rebuilt with bitcode enabled.

[craiggrummitt]

Framework needs to be rebuilt with bitcode enabled. Xcode 7 gives error:

DBChooser(DBAppearance.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

[smarx]

We should probably enable bitcode the next time we release, but in the meantime, you can add the code to your project directly and build with whatever settings you want, right? Or you can just disable bitcode.

[arkilis]

@smarx how to build the setting? thx

[Quentiu]

@smarx Will this be changed some time soon?

[greg-db]

I don't have a timeline for if/when we'll have an updated build with bitcode enabled, but I'm sending this along as a request to the team.

[coolnalu]

It's another year :-D

[thejeff77]

Can you guys build this? The DBChooser isn't usable without this. Coming up on 3 years later.

[greg-db]

@thejeff77 I can't make any promises, but I'm bringing this up with the team and requesting a new build.

Alternatively, there are some more native solutions that you may be interested in:

On iOS 10 we support Document Picker modes "Import" (UIDocumentPickerModeImport) and "Export" (UIDocumentPickerModeExportToService), but not modes "Open" (UIDocumentPickerModeOpen) or "Move" (UIDocumentPickerModeMoveToService).

On iOS 11, we support the File Provider extension (e.g., for use via UIDocumentBrowserViewController or UIDocumentPickerViewController). You can find information on the functionality provided by the Dropbox File Provider extension in the Dropbox help center here.

[thejeff77]

Thank you so much! I hope they can spend a few cycles updating this so it is useful again :)

[thejeff77]

@greg-db - it is still a more intuitive and direct experience for users to use this framework, as users need to enable dropbox to even show up in this document picker (which a lot of users have trouble with), and this document picker often lands users in weird spots.

I recommend that Dropbox either officially removes support for this library and updates documentation, or does the minimal work required to keep it working in order to maintain a uniform and consistently updated experience for dropbox library integration. Dropbox is a pretty big company - keeping externally facing libraries APIs and interactions consistent and working would be great!

[greg-db]

@thejeff77 Thanks for the feedback! I'll send this along to the team.