Library not found while building application through distribution certificate

[Maheshkmrao]

Hi Daniel,

While debguging with developer certificate the application is working fine in the device(iPad/iPhone ios version 8.0 and 8.4).

I am facing an issue while building the application through the distribution certificate and gives the error as :- library not found.

Please let us know the issue.

Thanks

[danielgindi]

Please go over the instructions in the README

[liuxuan30]

There are many posts already, like #240

try search and many answers

[Maheshkmrao]

Daniel -

We have verified the instructions in README and tried all those steps. However, its' working with Developer certificate on device, but nor with Distribution certificate. We have tried with other distribution certificate. But, still not working for them as well. So, do we need to revoke the distribution certificate as mentioned by liuxuan30?

Please suggest your thoughts.

[liuxuan30]

Based on your log, my problem isn't yours, because my footprint was

Library not loaded: @rpath/libswiftCore.dylib

Yours is

Library not loaded: @rpath/Charts.framework/Charts

Apparently the ios-charts library is not bundled in your app. You could start from here.

Quote from #240:

If you are building as a Framework, and have not dragged the code to the project, then it must be added as an Embedded framework. Otherwise the compiler does not actually embed the framework's code in the project - assuming it is available in the OS like any other framework - and will crash on runtime when it cannot load the library.

[rameshyadavmuddika]

Hi Daniel-

We hav fixed this issue by following steps:-

As read me we have followed each and every step but before building archive we need to do couple of steps as follows:-

We need have hav a new provision profile built with wild character as (com.XXX.*).

We need add this profile in build settings of project and we need to open the charts.xcodeprj and we need to change the bundle Id to (com.xxx.Charts) and include the provisioning profile and have the cer included

After this clean and build the app which is working fine now.

Thanks
Ramesh

[rameshyadavmuddika]

Provision with bundle id created for wild character as above because charts also should be mapped to thoes profiles

[liuxuan30]

So the reason is the charts.xcodeprj does not match your provisioning file and cert? I think this should be addressed in README plus the in-house distribution. @danielgindi

[rameshyadavmuddika]

Yeah your right @liuxuan30 that's why application is unable to compile the charts.framework while archiving the build.

[pmairoldi]

is this resolved?

[danielgindi]

I'm not sure how much we can do about this in an automatic fashion. I'm going to try to set the code-signing distribution to Automatic, see if this helps.
I guess this is an issue with all frameworks, and I wonder why Xcode does not know to build the framework with the parent project's cert. Strange.

[liuxuan30]

@danielgindi for the in-house distribution, we can do nothing but generate a new one.

[danielgindi]

So they always require generating certificates for Frameworks? Seems a bit strange as AppStore distributions work fine without special certificates

[liuxuan30]

I am not sure if it will affect AppStore distribution. But for in-house distribution, if the cert lacks the 'OU' attribute, it crashes for sure. BTW, I have to support iOS 7, so others are not tested on my side.

[wganeshb]

Is this issue resolved.
I am also facing the similar issue.
I can use development provisioning to run the app on device.
But it just can't archive the app using distribution profile. I get this warning whenever I validate the build.

[danielgindi]

This warning is OK. You can proceed.

‏בתאריך יום שני, 12 באוקטובר 2015, Ganesh [email protected] כתב:

Is this issue resolved.
I am also facing the similar issue.
I can use development provisioning to run the app on device.
But it just can't archive the app using distribution profile. I get this
warning whenever I validate the build.

[image: succeed with warning]
https://cloud.githubusercontent.com/assets/3005149/10422404/a24aa3c2-70d7-11e5-8fa2-17a8560dfc6d.png

—
Reply to this email directly or view it on GitHub
#266 (comment)
.

[wganeshb]

I proceed after validation warning. Submission is completed with warning as shown below.

[danielgindi]

It just means that they don't analyse IPAs of a few megabytes on the fly. You'll see the results in iTunes Connect

[wganeshb]

Thank you @danielgindi.
It is showing up on itunesconnect for beta testing..