Bug 129384 - Crash when tapping on the "movie" button in impress on iOS (app version 4.2)
Summary: Crash when tapping on the "movie" button in impress on iOS (app version 4.2)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-13 18:15 UTC by Nicolas Christener
Modified: 2020-01-16 10:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Screenshot (389.79 KB, image/jpeg)
2019-12-18 09:51 UTC, How can I remove my account? 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Christener 2019-12-13 18:15:13 UTC 
Description:
Impress on iOS (app version 4.2) has a "movie" button which probably inserts a movie into a slide.

Tapping this button will crash the app.

Steps to Reproduce:
1. Create/open a slide deck using the iOS app (version 4.2)
2. Tap on the "movie" button in the menu bar

Actual Results:
The app crashes.

Expected Results:
The app should not crash.


Reproducible: Always


User Profile Reset: No



Additional Info:
Tested with 4.2 (25) on iOS 13.3.x
Comment 1 Xisco Faulí 2019-12-16 18:37:11 UTC 
Moving to NEW
Comment 2 How can I remove my account? 2019-12-18 09:47:44 UTC 
I don't get a crash at the moment, but on the other hand editing presentations in the app is fairly impossible anyway, this has regressed like crazy in 4.2 it seems.
Comment 3 How can I remove my account? 2019-12-18 09:51:43 UTC 
Created attachment 156645 [details]
Screenshot

You mean this button, right?
Comment 4 Nicolas Christener 2019-12-18 10:00:45 UTC 
Yes, that's the button.

Crashes in all my tries (~empty presentation, complex presentation, ..).

Running 4.2.25 on iOS 13.3
Comment 5 Nicolas Christener 2020-01-14 15:19:22 UTC 
Tested in 4.2 (30). This issue is fixed and can be closed.

Thanks a lot to the Collabora team and especially to Tor for taking care of this.