The function to insert a "bibliography entry" leads to a crash of the iOS app.
This can be triggered on an empty document, I don't think further conditions are relevant (I use the "Empty (A4)"-template from the stock templates on iOS 13, if more details are needed I'm happy to provide them).
Steps to Reproduce:
1. Open a writer document using the iOS app
2. Tap on menu "Insert > Table of Contents and Index > Bibliography..."
The app crashes.
The app should not crash, a bibliography entry should be added.
User Profile Reset: No
That menu entry seems to invoke a UNO component that is not built for iOS. I am investigating whether it could be built, or whether it would then drag in other stuff that is not built either. The bibliography functionality is to some (unclear yet) extent married to the database functionality, and we don't provide Base in the mobile app.
In case this bibliography functionality would require building lots of stuff that so far has not been built for iOS, like the Firebird database engine which might be hard to build for iOS, would it be OK to simply not have that menu entry in the iOS app?
We have no need for that feature at the moment. It's perfectly fine if you just remove the menu item.
I hit the button accidentaly while presenting and found it out that way - not because we need the feature :)
OK, good, dropping it then for iOS.
Created attachment 155038 [details]
Initial attempt at patch, did not yet help, saved here for potential future reference
The crash is preceded by the warning "Uncaught com.sun.star.uno.DeploymentException component context fails to supply service com.sun.star.frame.Bibliography of type com.sun.star.container.XNameAccess".
Fix in https://gerrit.libreoffice.org/#/c/80889/
Tor Lillqvist committed a patch related to this issue.
It has been pushed to "master":
tdf#128177: Drop the 'Bibliography Entry...' menu entry in a mobile app
Fixed. I tested with 4.1.67 and I can't reproduce the issue anymore.
I think this issue can be closed.
Thanks a lot to the Collabora team and especially Tor for fixing this issue!