Crash after updating pods on iOS
See original GitHub issueHi!
After migrating my project from NS 4.2 to 5.1, it started crashing while calling firebase.init()
. I have been enabling/disabling features, but so far to no avail. Crashlytics shows me that it is around this (see full thread dump below):
5 nativescript 0x10c44bfeb -[FIRFirestore setSettings:] (FIRFirestore.mm:202)
Since this is something with FIRFirestore
, I already tried disabling Firestore (to try and isolate the issue) and rebuilding after deleting platforms
, but still same crash.
I was wondering whether someone is experiencing similar issues or if someone can understand what the problem might be from the crash log.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
CocoaPods Fails On Apple Silicon | Apple Developer Forums
Hi, I was trying to build my app on Apple Silicon on a DTK, but it fails, because the RubyGems is having some...
Read more >Pod Install crashes when building for iOS or macOS
I think there is an issue in the installed ffi.. First try doing pod install by arch -x86_64 pod install. if it fails...
Read more >'pod install' crashes on new and existing projects #920 - GitHub
After getting this error on an existing project, I created a brand new project for a mac app and added a simple Podfile....
Read more >Crashlytics on CocoaPods.org
Open Fabric.app, login and select the Crashlytics SDK. ... The Fabric app automatically detects when a project uses CocoaPods and gives you the...
Read more >iOS Xcode issue - App crashes after adding the cocoapods ...
I have an existing Objective-C project that is already using CocoaPods. After adding the pod 'Purchases' to my podfile my project no longer ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, you could move it to the
resolve
ofinit()
for instance.Thanks @EddyVerbruggen, yes I think it would be good to guard it like this, so at least we know what is going on.
Ahhh good to know what the reason is for the crash (weird though that the Firestore code doesn’t report anything!) So that means that, if I delay initialization of the FirebaseProvider until after firebase.init() then it should work…
Thanks again!