Manually adding Xcode library crashes build
See original GitHub issueI don’t know how I got my demo app working before, but it must’ve been pure luck. I revisited the app today. No changes had been made to the code since last Friday. While attempting to build it for iOS, the compiler crashed with a log file full of Swift errors. I have no idea why.
Here are the steps to recreate my issue.
If I remove libWatermelonDB.a from the project, the app will build in Xcode. If I remove/re-add the .xcodeproj file and the library. BOOM! Crashes again. It’s definitely not my app causing problems. It’s the WatermelonDB project.
I’ve tried multiple times linking/unlinking the library both through Xcode and using react-native link/unlink. I get the same result every time.
I’ve attached the project. Just unzip it, install node modules and pod files as usual. I hope someone can decipher what the hell the problem is. Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 by maintainers)

Top Related StackOverflow Question
Hello. @radex I had a similar issue today. No changes since last Friday, and today when trying to build the app I encountered all kinds of native errors.
I have Xcode 11.5 (latest) and tried to manually link again the library, removed the files and added them again, re-installing the library (but now I have v0.15.1 instead of 0.16.0 as before - I think latest release has changed - but the issue is the same).
Here is the log from
react-native run-ios:Hope this helps 🤞
At my next opportunity, I’ll get you more detail. For now, watermelon is not stable enough nor has the proper JSI for us to proceed with implementation.
You have a good start, but are in dire need of a retooling for ESnext and ReactNative > 0.60. Good luck.