same as bug#139350.

Works OK for me on a Samsung Galaxy S4 GT-I9505 with LineageOS 18.1 (based on Android 11) with daily build of 2021-05-23, (file name android~2021-05-23_05.05.31_LibreOfficeViewer-strippedUIEditing-debug.apk ), with and without experimental editing mode enabled.

Version 7.2.0.0.alpha1+
Build ID: 49af7e2

(In reply to baffclan from comment #1)
> same as bug#139350.

At least the cause is different this time, and I cannot reproduce so far.

There were some bug reports with similar error messages earlier (when opening existing files), but I was unable to reproduce those back then as well, and think all of them were closed in the end.

I just found bug 128101 comment 12, where it was also the case that you had such an error message (in a different scenario) that I could not reproduce and at some point it was working for you as well, but it's unclear why...

(Another mention of that error message I quickly found is bug 127781 comment 23, but that only happened for the affected person with a self-built version of the app.)

Some questions to narrow it down further:

1) What device and Android version are you using?
2) Does it work to open existing ODT files instead?
3) Does it work after uninstalling and reinstalling the app? (in which case cache,... are removed)
4) Can you possibly attach (the relevant part) of an ADB log (command "adb logcat" with USB debugging enabled on the device)?

(In reply to Michael Weghorn from comment #2)
Thanks for your reply.

1) What device and Android version are you using?
Sharp SHV43 Android 10

2) Does it work to open existing ODT files instead?
No. Similar error messages will be displayed.

3) Does it work after uninstalling and reinstalling the app? (in which case cache,... are removed)
I uninstalled and reinstalled it.
However, it did not solve the problem. 

4) Can you possibly attach (the relevant part) of an ADB log (command "adb logcat" with USB debugging enabled on the device)?
I don't know how to enable USB debugging and get ADB logs.

Bug 142618 (among others) mentions the same issue, but I'm still unable to reproduce (just tried on another "real device").

(In reply to baffclan from comment #3)
> 2) Does it work to open existing ODT files instead?
> No. Similar error messages will be displayed.

Thanks, that means there's a general problem loading files.

> 4) Can you possibly attach (the relevant part) of an ADB log (command "adb
> logcat" with USB debugging enabled on the device)?
> I don't know how to enable USB debugging and get ADB logs.

In order to enable USB debugging, you first need to enable developer settings on your device, which is usually done by tapping on the build version in the system information multiple times, then you can enable USB debugging in the developer options.

Retrieving and ADB log can be done by running the "adb logcat" command after setting up Android SDK tools on your computer and connecting the Android device via USB.
For Windows, there's a guide at https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClYXCA0 ; Linux distros often have packages providing the "adb" tool. Please just let me know in case I can be of any further help.

Also, do you remember what was the last daily build of Android Viewer with which this still worked for you?

Reproduce with Newest build.

Build Info
tinderbox: administrator: lohmaier+tinderbox@gmail.com
tinderbox: buildname: Android-ARM@86-TDF
tinderbox: tree: MASTER
tinderbox: pull time 2021-06-12 07:36:10
tinderbox: git sha1s
core:0c8fa16c78e6887d6d3a6041166d388e266bbce7


Thank you for the information on usb debugging.
I will try it.

I tried with USB debugging in the developer options enabled, 
could not get the crash log.