On Android, there's a bug (at least I think it is), when you convert from shortName to unicode. I'm using unicode, because I want native emojis on the devices.
I have an hybrid app, where you can make posts like in FB and other social apps, and of course you can post emojis as well. But as you know, there are emojis that are not supported on Android 7.1 & iOS 10 and down.
When it comes to emojis, if I start with an unsupported emoji, for example :face_with_symbols_over_mouth: then the rest of supported emojis listed right after the unsupported show as squares.
If I make a space between :face_with_symbols_over_mouth: and the rest of the supported smileys, then the supported smileys show correctly.
But if I have supported smileys before and after :face_with_symbols_over_mouth: then the supported emojis work fine.
It seems like supported smileys only get bugged, if I have :face_with_symbols_over_mouth: as the first smiley. On iOS it works fine, so seems like it's only happening on Android.
Hi all
On Android, there's a bug (at least I think it is), when you convert from shortName to unicode. I'm using unicode, because I want native emojis on the devices. I have an hybrid app, where you can make posts like in FB and other social apps, and of course you can post emojis as well. But as you know, there are emojis that are not supported on Android 7.1 & iOS 10 and down.
When it comes to emojis, if I start with an unsupported emoji, for example :face_with_symbols_over_mouth: then the rest of supported emojis listed right after the unsupported show as squares. If I make a space between :face_with_symbols_over_mouth: and the rest of the supported smileys, then the supported smileys show correctly. But if I have supported smileys before and after :face_with_symbols_over_mouth: then the supported emojis work fine.
It seems like supported smileys only get bugged, if I have :face_with_symbols_over_mouth: as the first smiley. On iOS it works fine, so seems like it's only happening on Android.
Can you look into this?