Summary: | Not possible to open, edit and save password protected files on iOS | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Nicolas Christener <contact> |
Component: | iOS Editor | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | aron.budea, tml |
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | iOS | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=129296 | ||
Whiteboard: | target:7.1.0 | ||
Crash report or crash signature: | Regression By: | ||
Attachments: | Pass is RockyTheDog42 |
Description
Nicolas Christener
2019-10-14 07:54:12 UTC
The attached files have "RockyTheDog42" as the password. Moving to NEW as agreed in the ESC meeting Created attachment 159565 [details]
Pass is RockyTheDog42
It's not possible to enter the password in the password popup in 4.2.4 (50) In 4.2.8 (62) the situation changed. It's now possible again to actually type in the dialog, so I can enter the password of a password protected file. However it seems, that the app "crashes" after entering the password. By "crashing" I don't mean, that the app disappears/closed but it is in a "unusable state" and must be manually killed. I have this now working, still double-checking and fine-tuning. See https://gerrit.libreoffice.org/c/core/+/103152 Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/808e8a8e9e96b6c3fac3ddf291e3900a40846409 tdf#128136: Build curl, nss, and xmlsec for iOS, too It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. This is fixed now. I tested with the iOS app version 4.2.10 (68). Thanks a lot to the Collabora team and especially Tor for taking care of this! I believe this issue can be closed now. |