dropbox-sdk-obj-c icon indicating copy to clipboard operation
dropbox-sdk-obj-c copied to clipboard

Linker error in manually integration

Open monish152 opened this issue 6 years ago • 7 comments

Hi, I am getting linker error like below screenshot.

screen shot 2019-01-13 at 11 58 52 pm

monish152 avatar Jan 13 '19 18:01 monish152

It sounds like you're using the "Manually add subproject" installation option, is that correct? Can you confirm that you followed each of the steps there exactly?

I also recommend going through the other potential solutions in the older issue (#146) if you haven't already.

greg-db avatar Jan 14 '19 16:01 greg-db

Hi @greg-db I have tried all steps as issue 146 but still getting same issue.

monish152 avatar Jan 14 '19 16:01 monish152

Can you share screenshots of your Build Settings for both the project and targets for both your app and the ObjectiveDropboxOfficial framework? Thanks in advance!

greg-db avatar Jan 14 '19 20:01 greg-db

Hi @greg-db attached files have screenshot.

monish152 avatar Jan 15 '19 15:01 monish152

screen shot 2019-01-15 at 8 30 30 pm screen shot 2019-01-15 at 8 30 20 pm screen shot 2019-01-15 at 8 30 08 pm

monish152 avatar Jan 15 '19 15:01 monish152

screen shot 2019-01-15 at 8 47 14 pm

monish152 avatar Jan 15 '19 15:01 monish152

Apologies I wasn't clearer, I was asking for the "Build Settings" tab in particular.

For example, I was just able to reproduce the error you're seeing with the following configuration: (note the different selections in the left sidebars, for different projects/targets)

screenshot 2019-01-15 15 39 26 screenshot 2019-01-15 15 39 28 screenshot 2019-01-15 15 39 31 screenshot 2019-01-15 15 39 34

I was then able to fix it by setting "Build Active Architecture Only" to "No" for both the ObjectiveDropboxOfficial project and iOS target. Can you give that a try?

I was also able to fix it by alternatively switching all 4 (across the app and framework, both projects and targets) to "Yes". The exact settings are up to you based on what makes sense for your use case, but to avoid this issue, you'd need to make sure these settings match. I.e., you need to build the framework for whatever architectures you're building for your app.

greg-db avatar Jan 15 '19 20:01 greg-db