Description
[REQUIRED] Step 1: Describe your environment
- Xcode version: 11.3.1
- Firebase SDK version: Firebase/Crashlytics (6.15.0):
- Firebase Component: Crashlytics
- Component version: 4.0.0-beta.4
- Installation method:
CocoaPods
(select one)
[REQUIRED] Step 2: Describe the problem
We've identified, that after signing the app with AppStore certificate, Firebase Crashlytics stops working. The problem does not occur while signing the app with AdHoc certificate. We are using Apple Distribution Certificate.
The errors we've found in the console:
<Forced crash, re-ran the app>
[Firebase/Crashlytics] Version 4.0.0-beta.4
..
[Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist
[Firebase/Crashlytics][I-CLS000000] Crash reporting could not be initialized
[Firebase/InstanceID][I-IID003014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 "The file “embedded.mobileprovision” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/private/var/containers/Bundle/Application/71738F66-30A3-4D4E-A60E-85F7FB3614AC/X.app/embedded.mobileprovision, NSUnderlyingError=0x282bc5b00 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
I've unzipped the ipa file and:
- there is Info.plist, it contains bundle identifier
- there is mobileprovision file, looks good.
The app would not even run without files above, so these errors seems like incorrect ones.
Steps to reproduce:
- Build the app with AdHoc profile, force a crash - works fine. Crashes are sent to Crashlytics.
- Build the app with AppStore profile, distribute via testflight.
- Install it from TestFlight, run, force a crash
- Re-open the app. Crash should be sent- it is not. Check out logs:
- Errors from Step 2 are visible.
Activity
JayachandraA commentedon Mar 9, 2020
Crashlytics, I'm also experiencing same problem. This is sending me the crash report in debug mode, but when I use signing the build and push to TestFlight it is not sending me the report.
yasirmturk commentedon Mar 10, 2020
Same here 👎
SeeTheInvisible commentedon Mar 10, 2020
We also have the same problem
terenceyan commentedon Mar 10, 2020
Also, seeing the same issue with an app not using
CocoaPods
installation. Using Firebase/Crashlytics (6.16.0).yasirmturk commentedon Mar 10, 2020
I have tried with both pods and with static framework linking using
6.18.0
samedson commentedon Mar 10, 2020
For others with the same issue, are you seeing the same log from Crashlytics and InstanceID? Eg:
Crashlytics gets the app's bundle identifier using
[[NSBundle mainBundle] bundleIdentifier]
- this seems to be returning empty.samedson commentedon Mar 10, 2020
If this is happening with both Firebase 6.15.0 and 6.18.0, it seems unlikely a code change caused this to happen, since many apps have successfully released to the App Store in that timeframe with Crashlytics. I'm trying to figure out what could have changed with Apple's signing that would cause this. It seems like files in general can't be opened from Crashlytics and InstanceID.
kondratk commentedon Mar 11, 2020
@samedson we are using
[[NSBundle mainBundle] bundleIdentifier]
in our app, and the method seems like working fine. Only Crashlytics has difficulties with accessing this identifier.kondratk commentedon Mar 11, 2020
@samedson
Haven't found any additional errors.
We are reading other files like translations of third party SDK's, so access is working fine. Also getting
[[NSBundle mainBundle] bundleIdentifier]
works as expected.samedson commentedon Mar 11, 2020
Want to ask a few more questions. I still haven't determined the root cause of the issue - wondering if maybe something changed with the timing of calling
[NSBundle mainBundle]
in iOS.[FIRApp configure]
in the App Delegate?terenceyan commentedon Mar 13, 2020
@samedson
Yes
A new app under development but on TestFlight.
Not using CocoaPods.
kondratk commentedon Mar 18, 2020
@samedson
FirebaseApp.configure() in App Delegate
We've just tried to migrate from Fabric SDK to Firebase SDK. There were no issues with Fabric SDK, so we've migrated back. Today I've received an email from Google that Fabric services will be held up and running until early May.
36 remaining items