-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[Xcode 15] iOS 14.5 crashing with Realm 10.42.3 #8369
Comments
This bug is similar like #8343. |
bump |
Same issue here. I've created a new project and just added Realm with SPM. It crashes on iOS 12 (device) and iOS 14 (simulator). Could it be related to this known issue with Xcode 15 new Linker ? (I tried the workaround but no luck) |
any solution for this? |
@Oreliano is it crash on iOS 14 device? |
I don't know, I don't have a device running iOS 14 |
Also having the crashes on Realm initialization since xCode 15. Crashes on initialization on both iOS 12 and iOS 14 (physical devices) |
I managed to resolve this issue after implementing the workaround method (Adding the If you are using RealmSwift via Cocoapods, |
I have this problem on physical devices (real users). Any official solution? No workaround |
As noted above you need to pass |
as above, -Wl, -ld_classic works |
Unfortunately the workaround only works for iOS 13 and 14. |
We have reports of this issue from users with iOS 12.5. |
Same on 12.5.6 |
I recommend reporting that to Apple as things not working on iOS 12 is not listed in the known issues for Xcode 15. You will need to use Xcode 14 until they fix it. |
There is no way to do it. We have a new bug with conflict of WKWebView with standard keyboard on iOS 17 if application is built by Xcode 14. There is impossible to analyse the new issue in that black boxes, so the only way is to use the latest software hoping for fast bugfixes. |
adding these doesn't work for me, My project can't build successful. |
same |
I'm facing the same issue for users running macOS Big Sur. |
Is the Realm team working on this issue? Should we wait for iOS 12 fix or switch to another framework? |
v10.43.0 fixed this issue for me 🚀 |
Just found how to solve the issue on iOS 12. In addition to the -Wl, -ld_classic flags, go to Build Phases > Link Binary With Libraries, add SwiftUI and set it to Optional. Also, be careful, there is an error in Realm latest changelog (-classic_ld instead of -ld_classic) |
Yep, thanks! Works for me as well now on iOS 12, 13 and 14 👍 |
It does not work for me, I try it on device system with 12.x、iOS13.x、 14.x , all Crash |
Yep thanks |
The release notes claim that this is fixed in Xcode 15.1, which was released today. |
@tgoyne Yes it's indeed fixed. Our app was crashing on jailbroken devices and updating Xcode to the latest version sorted the issue. We need the app working on jailbroken devices for pentest reasons. |
How frequently does the bug occur?
Always
Description
After building the app with Xcode 15 and Realm 10.42.3 (using SPM), it crashes immediately while starting it in the simulator with
Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)
.Xcode shows the following for this thread:
When building and running the app with Xcode 14.3.1 (14E300c) and also Realm 10.42.3, there isn’t any crash.
Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
It crashes always during app start.
Version
10.42.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
iOS 14.5
Build environment
Xcode version: 15.0 (15A240d)
Dependency manager and version: SPM
The text was updated successfully, but these errors were encountered: