-
-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot distribute inhouse build with ios-charts library embedded to my project #486
Comments
You might need to add a copy build phase and add the framework to that. |
If your cert already has OU attribute (this is a must and you never want to miss it), then it should be a project setting problem. Double check the build setting and build phase, and embedded framework, etc. |
Yes, OU attribute was not there in the old cert, so I created a new one, double-checked it, it is there. To be honest I cannot imagine what could be wrong. Only thing that comes up to my mind may be related to Carts.xcodeproj not having Inhouse configuration under Info - Configurations, which I "fixed" by copying and renaming the Debug configuration. May this be the problem? |
I would try searching for similar issues... There are many - and always resolved with simple steps after banging the head against the table for no reason... |
As I said, I tried literally everything. Many people on stackoverflow said it might be a bug caused by combination of XCode 7.0.1 and Swift 2.0. Will try building it with XCode 7.1 that came out today and see what happens. |
Any news? |
You may try the latest version where the tvOS target has been adjusted for Xcode 7.1 GM also |
I'm experiencing a similiar problem: DEBUG versions work, RELEASE versions crash ("Segmentation fault: 11"). In my case, this was due to the Optimization Level (Swift Compiler - Code Generation in Build Settings for Charts framework). When this is set to None I get no crashes, if set to Fast (which is the default for release versions) it crashes soon after the library is used. Charts v2.1.4, xcode 7.1. |
@tranq72 you need to provide the crash stack trace for such issues. Only saying crash can have many reasons. |
I will take it solved since no updates - closing |
Ok, I finally got to try it out, unfortunately, it still doesnt work. I am sure library is embedded correctly, I have even created a new certificate, so the Organizational Unit field is there. I am trying it with Xcode Version 7.1.1 (7B1005). |
I guess you have to try some demo projects or other ways, as we cannot offer much help without more details. |
I have this error too, and finally resolved it. This error shown on our device after we built and installed one version of .ipa file. The message is quit general , no details. After tries, I figured out it how to debug it, that you just connect your phone, open your project and hit "Run" button from your XCode, instead of makeing a ipa and install it on your phone, you'll see the real error message that causes this error msg. Once you disconnect your phone and see the log in XCode device, the "SecTrustEvaluate" error came again. |
the same problem happens to me ,an app installed in a jailbreake device ,lanunch and log this : Unable to obtain a task name port right for pid 601: (os/kern) failure (5) |
Hello,
first of all, I would like to thank you for creating this library. I have embedded it in my project (as written in the README file) by dragging it into the project, embedding it in the binaries and so on. Target iOS version is 8.0.
Everything worked great for dev version of the app, but as soon as I built the inhouse version, app crashes after initial welcome screen shows. Logs for the crash are as following:
The problem occurs here:
I tried creating new certificate, new inhouse build, basically went through all the stackoverflow questions regarding this or similar issue (eg. https://www.airsignapp.com/ios-apps-using-swift-crash-when-signed-with-inhouse-certificate/) without any success. Is it possible that maybe you need to change something certificate-related on your side?
Thank you very much for any answer
The text was updated successfully, but these errors were encountered: