https://bugs.documentfoundation.org/show_bug.cgi?id=112037
--- Comment #4 from Michael Weghorn <[email protected]> --- (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #3) > Michael, I'm no Android application developer. However, crash reporting > appears to be managed by Android at the OS level, since a consistent dialog > box appears when applications crash, and because crash reporting is > manageable via the Developer Options of Settings. Thank you for the input. I'm not familiar with the Android OS level crashreporting, but I'd generally also say it would make sense to use any capacities that Android already provides if that is sufficient, rather than doing anything extra on LibreOffice side for Android. I think the original request refers to having a similar capacity to what the desktop version currently provides ([1] has some more information). That one uses Breakpad and from a quick search, there is at least a README [2] for Android that suggests that it might work there as well. However, at least from the issues I have primarily seen on Android so far, they used to be either quite well reproducible and/or issues on the Java side or out of memory issues (like tdf#148851 or tdf#148854), for which I think (without having looked into that any further) that Breakpad probably wouldn't really be too useful either. For potential occasional (i.e. not reliably reproducible) crashes in the C++ code, many of those might already be caught by the crashreporting for the desktop version, since that one shares most of the code. I can only speak of my own experience so far, though, so if there should be good reason to still integrate it, it might be something to consider, which is why I set this to NEEDINFO for now, so in case anybody sees the need and has reasons for that, they can give more input here. [1] https://help.libreoffice.org/latest/lo/text/shared/guide/error_report.html [2] https://chromium.googlesource.com/breakpad/breakpad/+/master/README.ANDROID -- You are receiving this mail because: You are the assignee for the bug.
