I've found two stickers that telegram_backup identifies as the same (i.e. the same value is written to media_file into the messages table for both messages and one file is never downloaded).
I wonder if the issue is with Telegram itself but since it only appears in telegram_backup and not in Telegram Clients (I've tested this in the Official Telegram Desktop Client and the F-Droid FLOSS build of Telegram Android app - both show the two distinct stickers correctly)
Additional info:
The stickers belong to the same set,
the media_size attribute is set to the correct value for both of the affected stickers, and
the error is reproducible in that every time those stickers are used anywhere or if a completely fresh message backup is run (that is, after I rename the database file and rerun telegram_backup) telegram_backup would write the same filename for each of the two different stickers into the database (it is also the same name every time this occurs).
I'd readily share the affected stickers in a channel or so if necessary for debugging.
This seems to happen quite often in the following pack, for multiple stickers, not just the two I initially described: https://t.me/addstickers/AnimeReactions2M
I haven't seen this behavior for another pack yet.
I've found two stickers that telegram_backup identifies as the same (i.e. the same value is written to
media_file
into the messages table for both messages and one file is never downloaded). I wonder if the issue is with Telegram itself but since it only appears in telegram_backup and not in Telegram Clients (I've tested this in the Official Telegram Desktop Client and the F-Droid FLOSS build of Telegram Android app - both show the two distinct stickers correctly)Additional info:
media_size
attribute is set to the correct value for both of the affected stickers, andI'd readily share the affected stickers in a channel or so if necessary for debugging.