Maximize Your Firebase Crashlytics with Shipbook for Complete Log Management
With Shipbook, you can view the sequence of events leading to an exception captured by Crashlytics, making it a perfect complementary tool.
Stop trying to reproduce bugs. Just fix them!
Firebase Crashlytics is excellent for monitoring app crashes, but that's where its capabilities end. Shipbook, on the other hand, provides full visibility into all your app's issues and logs. Moreover, you can easily integrate Shipbook with Firebase Crashlytics for a full comprehensive solution.
Shipbook See the Full Story Behind Every Firebase Crashlytics Exception
No credit card needed ✦ Unlimited time on Free plan
No credit card needed ✦ Unlimited time on Free plan
Dror Yaffe
Co-Founder Bazaart
As a developer of a popular iPhone app there are many issues and bugs that I'm unable to reproduce. Therefore we incorporate very thorough logging, but up until Shipbook it was only available when a technical user would send us an email with the relevant information on his device where the information was logged. With Shipbook, we have access to all that information from a convenient dashboard. We can also cross reference the issue with other occurrences for different users and narrow down the causes for the bugs
Is it possible to use Shipbook and Firebase Crashlytics together?
I use Log Events in Firebase Crashlytics. How is that different from Shipbook?
Absolutely! Shipbook and Crashlytics work together in perfect harmony. Crashlytics alerts you when your app has experienced a crash and Shipbook will help you find out what caused the crash in the first place, displaying the logs that led up to the crash- thereby helping you solve the problem ASAP.
Integrating Shipbook with Crashlytics is a quick and simple solution. Once connected, you’ll be able to open the session of the crash and thanks to Shipbook, you’ll have the full picture and will be able to see all of the actions leading up to the crash.
Some users of Firebase also utilise Log Events, which is part of Firebase Analytics. This feature, which is limited to 500 types of events, is focused on analysis and not error handling. In other words, while Firebase may give you an indication of an error and its frequency it does not give you the information needed to understand why the problem occurred. This is exactly one of the basic functions of Shipbook.
In Shipbook there are no limits to the number or type of logs you collect. We don’t limit you to a specific length of text but rather give you the freedom to include any text for instance the full reply of a server or similar. In others words, with Shipbook you get the full log with all the relevant information.
Example:
You have a problem where a server continues sending a wrong message to the app. Firebase may give you information about the existence of the problem, but it will not give you information about what information the server sends, which is critical to understand and solve the error. By using Shipbook you get all the information including the full text that was sent from the server.
Continue using Firebase Crashlytics - Shipbook seamlessly complements it for a comprehensive solution.
Only Shipbook offers real-time insights into any problems your users encounter, along with the transparency provided by an open-source SDK. View all iOS logs, Android logs, and React Native logs leading up to each error, crash, and issue in your app, including the full text that was sent from the server.
What is the difference between Firebase Crashlytics and Shipbook?
Crashlytics is a great solution for reporting crashes in your apps. The problem is that it won’t catch all of the other issues that could take place in your app. This is the exact reason we developed Shipbook.
Most bugs and problems with apps do not lead to crashes, but are still important to fix. In cases such as these, Crashlytics, and any other solutions available targeting crashes, are of little help.
In addition, even in the event of a crash, having access to the logs of that session plays a critical part in understanding the steps that lead up to your app’s crash and thereby in discovering the solution to preventing future crashes.