Aves not scanning EXIF date correctly, applying wrong tags.

[safesyrup]

Guidelines

• I have read the guidelines to open issues

Steps to reproduce

1. Take photos with OpenCamera
2. Open Aves
3. Take other photos again with OpenCamera
4. Open Aves and see the photo in the wrong place

Expected results

The photos, when ordered by time, should be displayed in the order by EXIF date.

Actual results

There are two photos appearing in the wrong order. Both images have the incorrect date tag but a correct EXIF dates.

Screenshots or Video

No response

Logs

aves-logs-20260811_212026.txt

Custom environment

• I use a custom rom (if so, please specify below)
• I use a custom launcher (if so, please specify below)

Additional context

I am using e/OS 4.1.1 with blisslauncher.
I am hesitant to show screenshots of my library for privacy reasons, but the gallery looks as follows:

• ...other photos
• correct photo
  Date tag: Aug 4, 2026
  EXIF date: 2026:08:04 20:59:14
• incorrect photo
  Date tag: Aug 4, 2026
  EXIF date: 2026:08:07 14:03:58
• incorrect photo
  Date tag: Aug 4, 2026
  EXIF date: 2026:08:07 15:51:29
• correct photo
  Date tag: Aug 4, 2026
  EXIF date: 2026:08:04 20:57:17
• ...other photos

I am sorry that I cannot reproduce the result really, it's just something that I recognized when going through my holiday photos that few images seem to get the wrong date readouts. I am happy to provide further information.

[deckerst]

Thanks for the report.

Has your collection been scanned completely? When the scanning service runs, you can see a notification showing the progress (if you allowed notification).

If you select one of your photos where Aves shows the wrong date, then in the top right menu select "Rescan", do you still see the wrong date? If so, could you please do the following:

1. open the photo in the viewer,
2. go to its Info page,
3. tap the top bar for search,
4. select "Date & Time",
5. take a screenshot and attach it here.

Also, you could share some of these problematic photos with me via email.

[safesyrup]

Thank you for the quick response. Selecting the photos and performing the rescan action resolved the problem, thank you!
Is there a possibility to make the rescan option more visible/accessible? Even after your instruction I only managed to find the function via this GitHub issue comment of yours. Maybe a rescan all button or the ability to rescan a single image when having it open?

[deckerst]

Sorry I wasn't clear about the Rescan action location. It is by design that it is not visible/accessible, as it shouldn't be needed. It is only necessary when either 1) I introduce new metadata scanning features, which is rare, or 2) there is a bug like there is in your case. And I want to be aware of the bugs so I can fix them.

In your case, I'm interested to know if it happens again, with new items taken with your camera app.

By the way, does your app create photos of large size (say, 30+ MB)? As there are currently known issues where sometimes Aves scans a new photo "too early" as it is being created by the camera app, and this tends to happen with larger images.

[safesyrup]

No reason to apologize, it was more meant as a heads-up in case you have to mention it again :)
Ah, that makes sense then, thanks for the explanation.

If I see it happen again, would the app logs and steps I took until it happens suffice as information? What else could I look out for?

No, not really. The photos affected were 2 and 4 MB in size respectively, and I only have some panos up to 17 MB in size.

[deckerst]

If I see it happen again, would the app logs and steps I took until it happens suffice as information? What else could I look out for?

Knowing whether it's random, (in)frequent, steps and logs would definitely help. I don't know if there's anything else for now.