Last 3.12.0 destroy all libraries?!

[kelson42]

Claims a user:

Can you please confirm this is not the case?

[kelson42]

@MohitMaliFtechiz ... and please give a feedback to the user.

[MohitMaliFtechiz]

@kelson42 I have tested this and can confirm that it is not destroying the ZIM files. However, the previously added ZIM files do not initially appear on the LocalLibraryScreen. If we refresh by swiping down, all the previously added ZIM files reappear on the library screen.

Upon further investigation, I discovered the root cause of this behavior. It seems that the file path is missing from the book entity, and our validation logic checks if the file exists before displaying it on the local library screen. If the file path is invalid or missing, the ZIM files are excluded from the list.

This issue appears to be related to an automated change in the default.json file during the implementation of #3624. Specifically, the ID of the file property was updated here due an automated change, which inadvertently caused changes to our database. Due to this, previously saved file paths are now empty, leading to these files being filtered out during validation.

@MohitMaliFtechiz ... and please give a feedback to the user.

I have updated the steps on playStore on how he can get back their existing ZIM files.

[kelson42]

@MohitMaliFtechiz Can you please make a fix to fix this bad behaviour?

[MohitMaliFtechiz]

@kelson42 Yes, I am placing a fix for this issue, but unfortunately it will not work for those users who have already updated their app since the database of those users has already been updated.

[kelson42]

This is a pretty dramatic error. please put counter measure to avoid this happens again. I would at least put a heavy comment in the json around that ID to explain that this Id should bot change.