Hi all,
Crittercism
http://www.crittercism.com is one of the best crash reporting services available for iOS and Android. Also they provide a free plan and it's very easy to integrate. I'll be really glad if you can integrate their SDK to your games before publishing. So that if any crashing occurs, you can provide valuable information (such as frequency, device, OS version, etc) to Gideros team.
(Also you can use
http://www.crashlytics.com or
http://www.bugsense.com)
thank you
Comments
Likes: phongtt
Likes: TheOddLinguist
http://www.nightspade.com
https://sites.google.com/site/xraystudiogame
Website: http://www.castlegateinteractive.com
https://play.google.com/store/apps/developer?id=Castlegate+Interactive
@alexzheng I've tried to use your crash reports but I couldn't. Stack trace is really weird and I couldn't reproduce them.
@Scouser "I haven't seen any reports from flurry since 15th Dec 2012" yay!
Marc
1. Because of OpenAL context lost (I think I've fixed it with 2012.09.10).
2. Just at the beginning of OpenGL rendering like glClear. And still I'm investigating this issue.
I hope crash rate will be almost nothing after solving these issues.
Likes: alexzheng
@atilim, any insight into what this particular issue was? Not Gideros related, but I see crashes in another app that may be related to OpenAL context, but I can't figure out if it's the crash that is causing the loss of context or if the loss of context is causing the crash. Thanks. Paul.
On iOS 6, when user switches apps by double tapping home button, AVAudioSessionDelegate's beginInterruption is called but endInterruption isn't called. Therefore OpenAL context is not restored. Although I don't know exactly, it seems it's a bug of iOS 6.
For example, ObjectAL[1] also suffers from the same problem. I've filled an issue hoping to find a better solution: https://github.com/kstenerud/ObjectAL-for-iPhone/issues/46
I also know Codea[2] uses ObjectAL for sound playing. If you have Codea, you can observe same issue by switching Codea and Cargo-Bot[3] by double tapping home button.
[1] http://kstenerud.github.com/ObjectAL-for-iPhone/
[2] https://itunes.apple.com/app/codify/id439571171?mt=8
[3] https://itunes.apple.com/app/cargo-bot/id519690804?mt=8
I hope this post shows why I think Crashlytics is a good choice for a crash monitoring system.
EDIT: It looks like Android support is only in beta at present so that may affect your decision right now.
best regards
The program works fine on S3, Nexus 7, etc...
https://www.dropbox.com/s/agpmjaehtbbbqf3/MakeSomeNoise.apk
Any ideas why Crittercism isn't reporting the crashes?
https://deluxepixel.com
Most of your application errors will likely be Lua errors in your code. These will not show up in Crittercism at all, which is what I tried to indicate in my post here. When Lua gets an error it just outputs a stack trace and then exits the program normally. This will look like a crash but it isn't something Crittercism will detect.
The solution proposed in the above article isn't relevant to Android (yet) but the idea to save the stack dump to a file can be used by anyone capable of writing an Android plugin.
best regards
http://www.crashlytics.com/blog/its-finally-here-announcing-crashlytics-for-android/
do we need a plugin for it to make it useful? (to get lua crash info) i never tried anything like that before but should be handy.
Likes: SinisterSoft
Fragmenter - animated loop machine and IKONOMIKON - the memory game