… we aren’t getting your symbol files (NDK ), and therefore we don’t have the full set of information needed to display stack traces in plain text. I have been exchanging emails with Google’s Firebase support team, and what they have said so far is However, there is no useful information provided in Crashlytics, with each entry of the stack trace marked as “(Missing)”. It also reports the crash to Crashlytics, as expected (see screenshot). After running the app and clicking the button, the app crashes as expected. gradlew crashlyticsUploadSymbolsRelease command, as the guide instructs. In the C source of the app, I wrote code that forces a crash when a button is clicked. I have also followed the instructions in the “Get Android NDK crash reports” guide. That being said, I have successfully installed Crashlytics in the app and verified that it can report crashes. Not to mention, it seems that I am so close to getting Crashlytics to work. the multiple steps involved in the JUCE analytics tutorial just to get Goolge Analytics (a platform which is, at best, approaching its sunset) does not make me very interested in this approach. I was also not able to follow the tutorial, as it asks for a Google “ Tracking ID” this just does not seem to be a thing anymore (or perhaps ever) for Google’s Firebase platform.Īlso, given the relative ease in which I was able to install Crashlytics (this involved changing a few config files and 0 lines of code) vs. However, from my understanding, Google has recently acquired fabric.io’s Crashlytics (which is now also known as Firebase Crashlytics) and Google Analytics is on shaky (if not soon to be deprecated) ground ( see this JUCE forum post). However, I have hit a snag with Android (I have not yet tried setting it up for iOS yet).īefore I go any further though, I would just like to say that I know that JUCE has an analytics module, as well as a tutorial on how to use it with Google Analytics. I am writing a JUCE app for mobile (both Android and iOS), and would really like to have some kind of crash analytics in place so that I can provide better support to my users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |