Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 316 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
Crashlytics integration with Gideros app
I have been following the Bowerhaus tutorial on Crashlytics integration with Gideros (http://www.bowerhaus.eu/blog/files/luacrashlogging.html).
During my testing, I found that crash reports are not being sent to Crashlytics in case the exception happened inside a GTween complete event handler, such as this:
function onMouseDown()
breadcrumb("The user tapped the screen")
tween = GTween.new(info, 1, {y = 550}, {delay=0, easing=easing.linear, dispatchEvents = true})
tween:addEventListener("complete", function()
breadcrumb("tween completed")
unknownFunction() --this does not generate a crash report
end)
end
function onMouseDown()
breadcrumb("The user tapped the screen")
unknownFunction() -- this generates a crash report as expected.
end
Is there any special handling needed for such types of exceptions - either in the Gideros code or in the iOS plugin? Or could this be an issue with Crashlytics?
Any help is much appreciated.
During my testing, I found that crash reports are not being sent to Crashlytics in case the exception happened inside a GTween complete event handler, such as this:
function onMouseDown()
breadcrumb("The user tapped the screen")
tween = GTween.new(info, 1, {y = 550}, {delay=0, easing=easing.linear, dispatchEvents = true})
tween:addEventListener("complete", function()
breadcrumb("tween completed")
unknownFunction() --this does not generate a crash report
end)
end
function onMouseDown()
breadcrumb("The user tapped the screen")
unknownFunction() -- this generates a crash report as expected.
end
Is there any special handling needed for such types of exceptions - either in the Gideros code or in the iOS plugin? Or could this be an issue with Crashlytics?
Any help is much appreciated.
Comments
@bowerandy, may be you've encountered this?
I haven't experienced this directly but what I have seen is that there are some times that Gideros exits on an error and doesn't call the standard "C" exit() function. This could be one of those times. If this is the case then the exit won't be caught and the stack dump won't be written to the output file.
To verify this, try running the application under the XCode debugger and put a breakpoint in the exit() function to see if it is ever reached. If not, then this could be a question for @atilim to determine when exit(0 actually gets called.
Best regards
Thanks for your response. You are right. I tried running the app under Xcode debugger, and execution did not stop at the breakpoint I had placed in the exit() function.
@atilim, In which scenarios does the exit function get called by Gideros?
Any idea how to solve that?
https://itunes.apple.com/en/developer/unal-zubari/id953453674
or it's simple the method given on fabric page for android?
Fragmenter - animated loop machine and IKONOMIKON - the memory game
https://fabric.io/onboard/pending download their plugin and follow the steps it shows. It is really simple. I just added about 10 line codes then it was ready.
Edit:
They also have a Mac application for ios.
Fragmenter - animated loop machine and IKONOMIKON - the memory game