You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 2: Describe the problem
Steps to reproduce:
Got a crash previously and then it crashes every time when launching.
The console shows:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull dataUsingEncoding:]: unrecognized selector sent to instance 0x201ce80b0'
The fields being encoded there are all supposed to be nonnull fetches from plist files. If you're able to reproduce this crash on device, can you set an exception breakpoint and check which field is missing?
I'm submitting a PR to change the code so it will no longer crash, but depending on which field is missing you will likely see other issues, so definitely check that you identify what's causing the crash and fix it in your plists if necessary.
Step 1: Describe your environment
Xcode version: 11.4.1
Firebase SDK version: 6.24.0
Firebase Component: Crashlytics
Component version: 4.1.0
Installation method: Manual
Step 2: Describe the problem
Steps to reproduce:
Got a crash previously and then it crashes every time when launching.
The console shows:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull dataUsingEncoding:]: unrecognized selector sent to instance 0x201ce80b0'
After checking the source code in FIRCLSReportAdapter.m
It seems one of the strings being encoded in protoReport is NSNull.
The text was updated successfully, but these errors were encountered: