Make Crashlytics Better with Bugfender
Crashlytics shows you the crash. Bugfender shows you why it happened.
A Powerful Duo of Crash Reporting
Crashlytics is extremely popular for its user interface and the depth of its crash reports. Millions of developers around the world use it. But one thing it doesn’t do is log the user actions that lead up to a crash. Crashlytics is great at showing you when there’s a problem - it can’t always show you why it happened.
Enter Bugfender. By pairing Bugfender with Crashlytics, you will be able to log every single action your users perform, even when the device is offline, no matter where they are in the world. With our simple integration, app developers get the best of both worlds.
How It Works
Bugfender’s features work with Crashlytics to help make your app stronger.
Our remote web console enables developers to view the logs of their applications from real users' devices - wherever they are in the world. Bugfender’s 24-7 logging brings you way more than bug reports.
Assign custom information to any mobile device - like the user identifier in your database, username or email address. This allows you to access specific logs in seconds, leveling up your customer support game.
In-App Feedback from Users
In-App feedback tools make users feel heard and show you care about how their app looks and feels. Our in-app feedback feature lets you design your own screen, or choose our default version if you prefer.
You can configure Bugfender to send logs only when a specific condition is met. For example, you could programmatically send logs to the server only in the event of a crash or a failed assertion.
Your Customer’s Data is Yours and we operate by this principle. We don’t use your customer’s data, we don’t sell it to third parties, and we don’t target your customers with ads, tracker cookies or anything like it. Period.
Device logs are sent remotely from device to our servers, so you know what’s causing trouble before your users notice.
Enable and Disable Device Logs
Save your users precious bandwidth by only having specific mobile devices sending data.
Logs are queued on the device and are transmitted as soon as the device is online again.
Great Log Organization
Device logs are organized with a user centric approach. You can easily find what you’re looking for via our admin panel.
Customized Developer Notifications
Programmatically decide if you want to send logs if you detect a bug..
Detailed Device Info
The device version and operating system version are logged within each session, along with device orientation, free memory and other useful data to pinpoint what bug is happening where and why.
Tags & Log levels
Customize and prioritize your app log by setting tags and levels for each line to later search and filter entries within your iOS console log.
GDPR & Data Privacy
Bugfender is GDPR compliant and we'll be happy to sign a data processing agreement with customers.
Also you do not need to ask user for permission with the AppTrackingTransparency framework, since we do not do "tracking" in the definition of Apple. Read more
Keep track of your application's health in one central location with both logs and crashes.