Crash reports
complete
Peter Simic
After our app crashes, when the user returns back to it we want to ask them whether they would like to report that recent crash. If they tap "Yes", Shake opens up and the crash is reported the same way as a bug. With an addition of the stack trace, of course.
Log In
Peter Simic
complete
Crash reports with AUTOMATICALLY attached stack trace, screen recording, steps to reproduce and network requests are ready! Oh, and an optional user comment of what happened.
Properly developing a crash tracking and reporting product has been a monumental undertaking. We've been diligently working on this for MONTHS!
So you can use it today with 1 line of code :)
Just update your SDK to v14.2.
Read more: Shake Crash
Shake Crash is now available in our native Android and iOS SDKs, and not in the Flutter and React Native SDKs.
If you want to be perfectly safe, don't use it in production yet.
But please do use and abuse it when testing internally, and let us know of any rough edges you stumble upon. Our job is smooth them off now.
A
Arnaud Coomans
Peter Simic: Hi, I'm excited about crash reporting. I followed the instructions and updated the swift package to 14.2.0 (https://github.com/shakebugs/shake-ios), however building fails because it can't find either
Shake.configuration.isCrashReportingEnabled
and Shake.configuration.isAskForCrashDescriptionEnabled
. Am I missing anything? ThanksA
Arnaud Coomans
"Clean build folder" fixed it. Weird.
A
Arnaud Coomans
Peter Simic I'm getting the following error when submitting to testflight:
[Transporter Error Output]: ERROR ITMS-90035: Invalid Signature. Code object is not signed at all. The file at path [Tome.app/Frameworks/Shake.framework/upload-symbols.sh] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target.
. It looks like there's a upload-symbols.sh
file in the framework that probably shouldn't be there?M
Mrkva David
Arnaud Coomans: Yes, that script shouldn't be there. Please try manually removing the script from the Shake.framework before submitting to TestFlight. In the meantime, we'll fix this issue by removing the upload-symbols.sh script from the shipped Shake.framework so this issue shouldn't happen again.
M
Mrkva David
Arnaud Coomans: The fix for this issue is already in progress, you will be automatically notified when the fix is released.
A
Arnaud Coomans
Mrkva David: Great, thanks
P
Porter Hoskins
Peter Simic: Have you guys seen any issues with this conflicting with other crash reporters installed in the system?
Sanjin Grahovar Sadikovic
Porter Hoskins: Hey Porter. I’m Sanjin, the QA working on Shake SDK. We’ve tried it alongside tools like Crashlytics and a few others and we haven’t noticed any problems there. However, the feature is still in beta and we’re happy to help if you’re experiencing any issues!
B
Bahram Malaekeh
This feature will be a great addition to the tools Shake already has. Additionally, if it makes it easier to add the 'Realtime chat' feature, can't wait to try it out.
Peter Simic
Hi everyone, here's a quick update from our office: Our full focus
remains
on Crash reports and we still aim to release them this April. For free. For everyone.
Peter Simic
in progress
We're on it 👩💻
Peter Simic
planned