iOS client doesn't receive stickers sent from Android
It may be hard to describe how I actually got into this problem. Because at the beginning the stickers were actually delivering to iOS from Android.
I have an Android phone, Samsung S10+, Android 10. I have also installed a few sticker packs from this website https://signalstickers.com/ .
The sticker packs I installed (in this order):
At first there was no problem. All stickers were received by iOS. But after a few days I installed these new stickers:
And I noticed that people didn't receive those stickers from the last two packs. Then, some iOS users were able to receive those stickers, while some stopped receiving even the default preinstalled stickers.
The IOS version is 13.7, 13.6.1, 14.
Actual result: Stickers are perfectly sent from my device (Android 10), but not shown in the signal app on iOS (while there is IOS notification that a message was received) - there is nothing in the app, literally no message.
Expected result: iOS users receive and see stickers sent from Android.
Device: Samsung S10+ (Android 10), Apple iPhone XR.
iOS version: 14
Signal version: 4.71.5
IOS
https://debuglogs.org/9ced526ac6efe361eb9102252454bdb8736a534f9bcb643bf9706f3df03fcd3d.zip
Android
https://debuglogs.org/d76de1dfa0fd6b0a47fdccd84cce8f3123c2ad3d45f5e62093377f87649f4d4a


Hi,
Same behavior on Windows 10, Desktop client for me. If you don't install stickers manually you cannot see received one.
I'm seeing the same iOS behavior described by the original reporter (v3.17.1.1, iOS 12.4.1), from some Android users but not others. In the macOS desktop client (v1.36.1, macOS 10.14.6 build 18G6020), affected stickers are displayed as generic file icons鈥擨 can even click on them and download and view the stickers in other apps.
If this can help, the South Park sticker pack seems to have been created via the Desktop Sticker Creator tool, not from API or other mean. (source)
Thanks, we're aware of this issue. There is a bug in Signal-Android causing this behavior and hopefully it will be addressed soon.
@Imperiopolis-Signal should we mention the bug id here so it is linked?
Most helpful comment
Thanks, we're aware of this issue. There is a bug in Signal-Android causing this behavior and hopefully it will be addressed soon.