-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
I took same error. I returned the 1.1.1500 version then its fixed. #154
Comments
Most likely because something cached old version for you (Cocoapods? DerivedData? Xcode project?) and do not fetch newer version properly. I'd love to know the problem, but from my investigation there's no setup changes between 1.1.1501 and 1.1.1700 other than updated binaries. Notice the previous version: 1.1.1501 |
I see, but i depended openssl-universal from a pod. I didn't add openssl directly to my podfile I executed these commands;
And i got this error at the runtime. Then I noticed a difference in podfile.lock. OpenSSL-Universal version was changed. If i add to OpenSSL-Universal 1.1.1501 version to Podfile, I don't get the error. note, i have tried the delete derived data and clean project. |
try one more
I'd give it a try with new sample project. I wonder if you can reproduce it there. |
With 1.1.1700 the app crashes right away, saying OpenSSL cannot be loaded. With any older version such as |
can you reproduce it with a newly created sample project that you may attach here? |
Actually with 1.1.1700 the app works on simulator, but on the real device it crashes:
You can send me over sample project to test. |
as I said before. It looks like an Xcode project (maybe Cocoapods) issue where it does not embed framework in the app bundle properly for some reason (??) |
But why does it work with the older versions? There has to be some breaking change? |
I don't know tbh #154 (comment) can you send me this test project you created? |
It's not the test project, I've just replaced the IDs. I see 3 commits after 1.1.1501, one of them is definitely breaking things: Maybe to reference a specific commit in Podfile instead of using |
not sure what you mean by that, there's a single commit between 1.1.1501 and 1.1.1700 9429bf8 |
Doesn't work: Works: |
Doesn't work on your project. can you reproduce it with a newly created sample project that you may attach here? #154 (comment) |
I've created test project and it crashes even in simulator. Just download it, do |
pod version 1.11.3 Are you running the same? |
The issue is reproduced on the new empty project on the Mac with M1 chip when the terminal is not running in Rosetta mode. |
getting a similar error with OpenSSL-Universal 1.1.1700, app crash while we tap on the app icon Termination Description: DYLD, dyld: Using shared cache: EC12EBDC-CAE3-34EC-ACCB-0B6E5ABC73EB | dependent dylib '@rpath/OpenSSL.framework/OpenSSL' not found for '/private/var/containers/Bundle/Application/62AEA174-7CD0-4D1A-9DEA-86183FBFAD2A/mID Verify.app/mID Verify', tried but didn't find: '/usr/lib/swift/OpenSSL.framework/OpenSSL' '/private/var/containers/Bundle/Application/62AEA174-7CD0-4D1A-9DEA-86183FBFAD2A/mID Verify.app/Frameworks/OpenSSL.framework/OpenSSL' '@rpath/OpenSSL.framework/OpenSSL' '/System/Library/Frameworks/OpenSSL.framework/OpenSSL' Backtrace not available Unknown thread crashed with ARM Thread State (64-bit): Binary images description not available Error Formulating Crash Report: EOF |
I got similar error with @Dhananjay-Fartyal. My mac is intel based. can it be related with that ? |
is it all related to CocoaPods setup for everyone, or do anyone see issues with SwiftPM setup too? I still cannot reproduce it on my end and can't really do anything about it. |
@mketizmen Yes, My mac is Intel-based, and I don't think it is chip related issue, Somehow OpeSSL 1.1.1700 framework is not embedded in my app which causes crashes, I downgraded it to 1.1.1501, which works for me. It seems cocoapod issue with this version (maybe architecture), still investigating the exact root cause. |
Hello @krzyzanowskim, my team can reproduce this issue on both Intel and m1 macs using SPM. It doesn't seem cocoapods related |
I still cannot reproduce it on my end. Just yesterday integrated 1.1.1700 as SPM in new app and it worked just fine here (Xcode 14) |
I'm happy to continue trying to reproduce. send me a project and exact spec so I can be as close as possible and see if I can reproduce |
That said, we can setup up a pair debugging session and try to diagnose and solve the problem on your machine. that exceed the free support for this project I can provide. |
Don't worry, we will try to investigate the reason on our side first. Just wanted to mention that it's not specifically cocoapods related as you asked the question :D |
Running into this issue when using OpenSSL via SPM, I setup an example project here that hits the issue only on physical devices and when embedding openssl in a sub framework. https://github.com/jacoblange-dev/OpenSSLBugExample |
UPDATE
it actually works for me, the diff is gone, and the framework folder now has OpenSSL.framework and content correctly. It should be a nasty bug from cocoapods core's dependency or code. I notice on the working macOS, the framework folder contains correct OpenSSL.framework, while on my mac, it's named OpenSSL-Universal and has no content. Not sure if this helps. On my side, I met similar issue as well, same git branch, same Podfile.lock, nothing touched, once I do pod install, it will have below diff: but on another macOS, same pod 1.11.3, it will never have this diff. and in the simulator it will carsh as framework not found. |
I took same error. I returned the 1.1.1500 version then its fixed.
I think, 1.1.1700 build has a problem. @krzyzanowskim
Originally posted by @burakCokyildirim in #152 (comment)
The text was updated successfully, but these errors were encountered: