Bugfender for iOS
Cloud Logging and Management
Bugfender is a cloud-based service that allows developers to upload their app logs — even from remote devices — and then view them on an organized Web console. Simply create an account to start using Bugfender to get the NSLog console of any device your customers are using your mobile app on.
Integrate Our SDK in Less Than 60 Seconds
We also provide an SDK via CocoaPods with a better logger than NSLog, making it very easy and powerful to send logs to Bugfender. Our small footprint SDK takes up little memory, so your mobile app performance won’t suffer at all.
Adapt Our Remote Logger to Your Needs
Bugfender has more advanced features than the standard iOS log system with NSLog. Our remote logger allows you to programmatically decide if app logs need to be sent to the server or directly alerting the developer of an error condition that needs to be investigated.
Works with Apps in Any Stage of Development
Bugfender works well in applications in production, published in iTunes Connect, published beta versions (like Testflight) and enterprise applications published in a corporate store.
Track Your Application's Logs Remotely
NSLog or Custom Log
iOS device logs are sent remotely from device to our servers, so you know what’s causing trouble before your users notice.
Enable and Disable iOS Device Logs
Save your users precious bandwidth by only having specific mobile devices sending data.
Logs are queued on the iPhone or iPad and are transmitted as soon as the device is online again.
Great iOS Log Organization
iOS device logs are organized by sessions, devices and app versions. 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 iOS Device Info
The iOS version and iPhone, iPad or iPod 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.
Learn How To Install Bugfender iOS SDK in 10'
Watch this simple tutorial and learn how to receive the NSLog logs and crashes form your users.
What Are 1000 Apps Doing to Reduce Their Bugs to Zero?
Down to Zero is a practical guide to solving bugs. Our team has been developing mobile apps for over a decade and we'd like to share some tips we've picked up along the way.
What Do Our Customers Say?
Bugfender is helping thousands of developers all over the world to release superb, bug-free applications.
We leverage a ton of sensor data and having the ability to remotely enable/disable logging for troubleshooting has saved us so much time in guessing what may have caused customer issues. Billy Lo from Sidekick-App.com
Our code was developed by a third party, we had no insight as to how things worked in the field. After having major problems, we asked them to integrate Bugfender. It was quick to setup and we were instantly able to discover issues and troubleshoot ourselves. Without Bugfender, we'd have been pretty sunk. Roberta Hendricks
Bugfender has allowed us to catch issues that we could not find previously while test driving cars. Nabyl Bennouri from CARFIT
Just wanted to tell you guys, we are loving Bugfender. Don't know how we made it this far without it. We used to use Lumberjack, but then it didn't support Swift. And, it was always awkward to get log files off devices. Now that is trivial. Nice job! Great web interface. Steve Webha from Blast Motion
On many occasions Bugfender enabled me to look into a bug before the QA had even reported it. David Dunham