few times libreoffice viewer is crashing. can you please add crash reporting on daily builds. if possible provide link for crash report [ crash id ] sent to crashreport.libreoffice.org after the submission by email or in app itself [ similar to about:crashes on fennec ]
set as new
Do you still see these occasional crashes that might provide a reason to enable crashreporting? Haven't looked into this yet, but I suspect that (if it's reasonably possible on Android) this would also mean that the app/APK size would increase due to more libraries/... that are needed, and I'm not sure whether that's actually worth it.
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.
(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
Dear vihsa, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear vihsa, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp