Bug 123699 - Crash when opening the second file
Summary: Crash when opening the second file
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-02-25 10:52 UTC by Nicolas Christener
Modified: 2019-03-14 20:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
App crashes after opening the second file. (385.65 KB, video/mp4)
2019-02-25 10:53 UTC, Nicolas Christener 		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-02-25 10:52:33 UTC 
Description:
After opening + closing a document and then opening the next file (doesn't matter if it's the same or a different file), the iOS app 0.1 (17) crashes.

Steps to Reproduce:
1. Open a file in the iOS app
2. Close the file
3. Open the same or a different file (again)

Actual Results:
App crashes

Expected Results:
App opens the chosen file


Reproducible: Always


User Profile Reset: No



Additional Info:
This happens in 0.1 (17), please see attached video.
Comment 1 Nicolas Christener 2019-02-25 10:53:15 UTC 
Created attachment 149572 [details]
App crashes after opening the second file.

After opening and closing a file and then opening the next file, the iOS app crashes.
Comment 2 Nicolas Christener 2019-02-27 07:46:44 UTC 
I checked this in 0.1(18) and it seems to be fixed (this was also mentioned in the release notes).

Therefore closing this one.

Thanks!
Comment 3 Xisco Faulí 2019-03-14 20:01:32 UTC 
(In reply to Nicolas Christener from comment #2)
> I checked this in 0.1(18) and it seems to be fixed (this was also mentioned
> in the release notes).
> 
> Therefore closing this one.
> 
> Thanks!

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.