I'm not sure why Crashlytics didn't show me where is the line crash
i have follow all the integration instructions and read the documentation but still no result
and i'm sure that i've been upload the right dSYM file
its just showing me something like this screenshot
and i've been looking around and they said to do this
but it doesn't help
any idea?
This is a known issue that happens with some bitcode enabled apps. It seems to be a bug with how Apple is regenerating dSYMs and we've (Fabric) submitted a report to them about it.
In the meantime, if you turn off bitcode and rebuild then you should be all set for future crashes.
Related
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
Will Crashlytics Track User Crashes if it is Complaining About my Missing dSYMs?
I believe my issue is that "$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)" for XCODE 10 might not know where to look since I have a dev and prod info.plist file, but Firebase Crashlytics website doesn't say much about this.
If you don’t upload the dSYMs, it will captures the crashes, but it doesn’t include them in the standard reporting. But you can retroactively upload the missing dSYMs and the crash reports will suddenly become visible/usable.
For previous releases, you might check https://appstoreconnect.apple.com, as there’s a link to download the dSYMs there, which you can then upload to Crashlytics. I’d suggest referring to the Crashlytics document titled Get deobfuscated crash reports for the process of making sure you get these dSYMs uploaded in the future.
Also see TN2151: Understanding and Analyzing Application Crash Reports for broader discussion of dSYMs. Also see WWDC 2018 video Understanding Crashes and Crash Logs.
My main app binary is not symbolicated correctly. But I see symbols from frameworks built with help of CocoaPods.
It is the same problem as described in this question:
Resolving problems in XCode 7 crash reporter
But answers for this question is not resolve an issue absolutely.
It's crazy to re-symbolicate reports every time manually.
And it's not really forward-looking idea to turn off bit code.
I fill the problem is somewhere in project configuration. Looks like CocoaPods do this the right way but I can't find suitable configuration for my app.
Do anybody know solution that solves problem fully once and forever?
Here the same project crash with bitcode turned off:
I have the error: "It looks like we are missing dSYMs to process crashes for the versions below." - I have downloaded the dSYMs in the Xcode organiser, found the .xarchive and zipped the corresponding dSYMs folder and uploaded with success; but the error does not disappear i.e. does nothing:
How can I symbolicate my crash reports?
dSYM Folder:
I just had the same issue and searching for solutions brought me here. Since this is missing an answer and I solved the issue for me, I'll resurrect this question to maybe help others having the same issue in the future.
Below the part shown in your first screenshot, there should be a list "REQUIRED (These are needed before crashes can be processed)" stating which UUIDs are still missing their dSYM and from which Build they are.
Just download the dSYM of the respective Build(s) like stated in the official Docs » Crashlytics » All about Missing dSYMs.
(E.g. log into iTunes, select the respective Build and click on download dSYM at the Build Details screen)
The downloaded dSYM(s) can simply be manually uploaded as you already did the other file(s).
I've tried almost all the variants, described here on stack overflow and on Fabric info page, to solve the same issue. But, unfortunately, none of them helped. And I've found a new solution, which I haven't seen here on Stackoverflow and which fitted me.
I've integrated HockeyApp with the project of my app and uploaded the build into HockeyApp (the build is uploaded there with an archive which contains dSYMs). After that the crashes started finally appearing on Crashlytics as symbolicated crashes with details.
I just had the same issue. The reason was enabled bitcode. So disable it or download dSYMs from iTC and upload them manually. I didn't find bette solutions yet.
I've just created a new iOS Swift project, using Xcode 7 beta-4, and have integrated Crashlytics (part of Fabric now) with the usual process.
It integrated all fine, and I can simulate crashes etc.
However when I go to the Crashlytics dashboard it warns me that:
Missing dSYM
We're missing a dSYM to process crashes, upload it here!
And none of the crashes show up.
Clicking the warning message (it's link is mentioned here:
http://docs.fabric.io/ios/crashlytics/crashlytics.html#troubleshooting) gives me a list UUIDs Crashlytics is missing dSYMs for.
The page gives the option to upload a dSYM, which I have tried doing (getting it from /Users/me/Library/Developer/Xcode/DerivedData/MyApp-xxxxxxxxxxxxxxxxxxxxxxxxxxxx/Build/Products/Debug-iphoneos). However after doing so this does not resolve the issue.
I've tried getting the frameworks from CocoaPods instead of manually adding them, in case that made a difference. It didn't.
-
So my only thought is perhaps Crashlytics doesn't handle dSYMs produced by Xcode 7 beta? Or is there something fundamental I've overlooked?
Many thanks for your help!
-
UPDATE:
After many back and forth emails with the Crashlytics team, this particular problem was discovered by them to be caused by changes made in one the beta Xcode 7 versions. A fix to Crashlytics was pushed out and since then it worked.
If you're experiencing similar issues, I suggest first ensuring you're using a release version of Xcode, and also the latest version of Crashlytics :)
Go to Build settings and choose Dwarf with dSym File option for both debug and release builds.
You haven't uploaded dsym ..You can get dsym file from:
Goto https://itunesconnect.apple.com> SignUp> MyApps> Activity> Then select the version of App for which the Missing dsym error is showing and download the dsym file from there...
upload it to fabric
Hope so your issue is resolved..