nextcloud / nextcloud/talk-android
❤️ Heart emoji inconsistant between Android and iOS
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- Get an Android Talk user to react with a ❤️ on a message.
- Get an iOS user to react with ❤️ on the same message.
Expected behaviour
It should show: ❤️2
Actual behaviour
It shows: ❤️1 ❤️1
Device brand and model
Samsung S24 Ultra
Android version
16
Nextcloud Talk app version
22.0.3
Nextcloud server version
32.0.1
Talk version
22.0.4
Custom Signaling server configured
No
Custom TURN server configured
No
Custom STUN server configured
Yes
Android logs
No response
Server log
Additional information
Looks like this in the app:
And in the web:
Couldn't the solution be, to just add the ❤️ instead of some unicode or whatever is added there? And should I open an issue request for double-tapping for the heart emoji reaction?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by adding the same heart reaction from Android and iOS to one message, then inspect the Talk Android reaction handling and rendering entry points; no file or test is named in the report. The fix is done when equivalent heart reactions are grouped as ❤️2 consistently in the app and web views, with coverage for both clients if the project’s existing tests support it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100