Rotate corrupts files about aves

[deckerst]

I couldn't reproduce the issue, after trying with all these combinations:

• file format: JPG / PNG / WEBP
• storage volume: primary / SD card
• Android version: 8.0 / 10 / 11

I noticed there's a minor issue (the viewer sometimes does not refresh after rotating), but in any case no file got corrupted.

To investigate further I would need more details from you:
Does it happen all the time or randomly?
When it happens, is the file on the primary volume or something else?
Is the folder containing the file a special folder, like "Downloads"?
What is the file format?
Does Lineage OS have a different permission system, compared to vanilla Android?

[deckerst]

I will close this issue but feel free to reopen it if you can provide further details.

[a1danial]

This error occurred for me. The original picture was fine then after rotating, a large section of the image turned blank. Attached the original picture and the screen recording of the error

screen-20230621-235848.mp4_2.mp4

[deckerst]

Thanks for letting me know.

Could you paste here your environment info and logs (following instructions in About > Bug Report)?

Also, did it happen just once? several times randomly? all the time?

[a1danial]

Package: deckers.thibault.aves
Installer: com.android.vending
Aves version: 1.8.9-play, build 100
Flutter: stable 3.10.3
Android version: 13, API 33
Android build: T1.5-230428-2017
Device: Nothing A063
Geocoder: ready
Mobile services: ready
System locales: en_GB
Storage volumes: /storage/emulated/0/
Storage grants: /storage/emulated/0/Pictures/, /storage/emulated/0/DCIM/, /storage/emulated/0/Download/1DM/, /storage/emulated/0/JockeyAlbumArt/, /storage/emulated/0/Android/media/
Error reporting: true

Logs:
aves-logs-20230622_005737.txt

Happen this once

[DodoLeDev]

I faced a similar issue while tagging videos:
Sometimes (it's quite rare for that to happen), when I tag mp4 videos, Aves returns Success!, but the file is no longer readable (with a big Zut!)

I can reproduce the issue with the involved files, but I can't share them with you because of privacy concerns.
For now, I haven't found any file I can afford to show you that has this problem...

[deckerst]

@DodoLeDev if you don't want to share them publicly but you trust me personally, you could send me the files by email.

Also, if someone experiences this issue, please save the logs right away and attach them here.

[deckerst]

@a1danial do you use a custom ROM or some special security/memory features?

Also, do you know whether it happened when memory or storage was low?

I tried to reproduce by editing several hundreds files multiple times and I can't reproduce the issue :/