Blog

25 Nov 2015 - Bulletins and App

Crashes

The latest versions of Bark’n Mad, Bark’n Mood and Noise Monitor include the capability to display a web based bulletin. I can target the distribution of a bulletin to a specific app version or a specific users device. Part of the information I receive from a crash report is a unique identifier for your device. The app’s above look for a bulletin with your device identifier. The reason I’ve done this is that I’ve recently seen some crashes which could easily have been avoided if only I could have contacted the device user. This is not an invasion of your privacy as I still do not know who you are.

7 Oct 2015 - App Beta Testing

The Crashlytics framework provides us with another testing tool, a beta program. We can now distribute a new build to multiple testers or to an individual with a specific problem without having to wait for around a week for a new app version to be approved on the app store. If you have a problem that you can’t work around and are prepared to trial a beta version then let me know by email.

22 Mar 2015 - App Error

Reporting

When an app crashes your iPad or iPhone returns to the current page of the main screen. That is the app simply disappears and you revert back  to the previous page of app icons. My apps use a framework called Crashlytics to capture crashes and report on them. To send me a crash report the only thing you need do is open up the app again, crash reports are sent the next time the app is opened, not when the crash occurs. None of your information is sent in this report. All I get is an analysis of what the app was doing, where the error occurred and the log entries from the app. As far as you are concerned I also get a unique identifier for your device (one of my devices is: 887B0E03-BD99-4F9A-863C-B03F274C743C) and the name you have assigned to your device (e.g. ‘Johns iPad 3’).