I tried to setup Firebase Crashlytics for our iOS project but I wasn't able to get valid crash log...
What I did so far:
Created a new "helloworld" iOS project
Added Firebase (Analytics & Crashlytics) by using SwiftPackageManager
Created the project within Firebase
Added the GoogleService-Info file
Called the init within the AppDelegate
Placed a button to force an unwrapping of a null value
Archived the project by using XCode & enterprise certificate
Located the archive and extracted the dSYM-file
Uploaded the dSYM-file by using the upload-symbols tool
Exported the archive as enterprise signed IPA
Installed the enterprise signed IPA on my device
Clicked the button and let the application crash
The crash is displayed within the firebase project and the section dSYM doesn't complain that some of the dSYM files are missing. Even though the crash isn't readable at all...
Has anyone managed to display crashed in firebase with a comparable setup? Just found the information that sometimes it's necessary to uploading the dSYM file provided by App Store Connect (Which is impossible for my enterprise solution...)
Related
I have a Safari extension in the macOS App Store. The Xcode project was created using the safari-web-extension-converter. It creates 4 targets, 2 each for iOS and macOS. I've done a number of releases of the macOS version successfully.
When I build and archive the iOS version, this completes successfully. When I attempt to upload the archive, I get this error after at the last Upload step:
App Store Connect Operation Error
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'michaelanthonyflores.Passport-Extension' under the iOS application 'Passport Extension.app'. With error code STATE_ERROR.VALIDATION_ERROR.90685 for id d8a52342-9686-4d7a-acec-93ce5dfb5d56
This is confusing since I don't have an existing iOS application in App Store Connect. Previously I attempted changing the name and ended up down a rabbit hole of signing and identity errors. What is the actual issue that this usually points to? How do I get more helpful debug information on this?
I have implemented a Firebase crashlytics in my project, and also I have configured the firebase account with my project. But when I do a crash with the help of Crashlytics.sharedInstance().crash() I will get crash crash report perfectly. But if I do a crash with any other method, it is not showing up the crash report. But some crashes are showing in the dSYMs tab in crashlytics and it is not formatted correctly. I have downloaded the dSYM file from the iTunes store and uploaded to Crashlytics through terminal. But Still I am getting the crashes in the dSYMs tab and not formatted correctly.
This is How I am getting crash report in dSYMs tab in Crashlytics.
Does anybody know what I am doing wrong here?
I could able to implement it in my Swift project and it correctly decrypted the errors and displayed correctly. But when I implemented it into my Objective-C project, I am not getting the correct decrypted report.
When having "optional" missing dSYMs, those are usually related to .frameworks or other third party library being used. If you only have these kinds of missing dSYMs, the dashboardwill show the crash report, but the frames related to those dSYMs won't be symbolized.
DSYMs marked as "required" are related to your main app, when those are missing, the dashboard won't show the crash report.
Usually, when using a .framework, the dSYMs files should also be available, but if not, you'd probably need to get them from the framework owners.
To elaborate Gerardo's answer further, please refer to your Xcode Organizer. There goes a list of your app published with different version. Download the dSYM
reports first and hence follows the procedures given from Google and submit those dSYM to firebase
Make sure you have already installed the latest version of FirebaseCrashlytics via Cocoapods and proper app profile at your Firebase Console.
https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports#upload-dsyms
How can I add the Dsym file using the upload script even if I didn't updated the Crashlytics version? I have the 3.14.0 version of it so I don't have the FirebaseCrashlytics directory in and I just published my app. Now I'm stack because in the Firebase console -> Dsym screen, it gives me only the way of use the script and not the old way (upload the Dsym file from my Mac manually).
Right now, I can see few crashes from Xcode -> Organizer but I'm not sure that all the crashes are tracked in it.
Fabric/Firebaser here - if you're on the legacy Crashlytics SDK, you'll notice that rather than having something like FirebaseCrashltyics.framework imported into your app, you should have something like Crashlytics.framework. Either one has an upload-symbols script as part of the installation, so use whichever one is supplied as part of the Crashlytics installation. Attaching two screenshots to show the difference.
legacy Fabric Crashlytics
Firebase Crashlytics
Integrated google firebasecrahlytics in my project.
I have noticed when running my application through the simulator and force a crash, i am able to see the crash report correctly as in attached screen shot.
when i created an .ipa with bitcode enabled and force a crash, i am able to see the crash report with Compiler generated reports at line 0
when i created an .ipa keeping bitcode enabled and upload dysm manually and force a crash i am able to see the crash report with getting __hidden#587 reports.
How can i get the correct reports as of simulator.
please note my applications are not in the app store and I do not have itunes connect I am using an enterprise account.
PFA screen shot
I am trying to get crash reports working on my ios app. I am getting an error message in the Firebase Crash dashboard that says
Upload symbol file to symbolicate future stack traces for UUID 69696969-7F8H-567E-1ABCD-FAKEID123
I have checked every binary on my machine, and not a single one of them has this UUID. So where is this UUID coming from? I put a fake one in the example above obviously, but how can Firebase be asking for this UUID if it doesn't exist?
Note that this is a test crash. I am calling
FIRCrashMessage("Hey man, you crashed.")
fatalError()
in my app. The build is one I've downloaded from iTunes connect via TestFlight. Is Apple creating a binary that I don't have a dSYM file for? I have bitcode disabled.
I also verified that the run script is working. If I click "Symbol Files", to the right of "Dashboard" on the Firebase Crash Reporting tab I have lots of dSYM files uploaded to the Firebase Crash service, but none match the UUID of the binary I've downloaded from TestFlight.