RocketChat / RocketChat/Rocket.Chat.ReactNative
Reply to a message on AppleWatch not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 1.5k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 90
Description
Description:
When you get a message while the iPhone is in sleep mode, the push notification gets diverted to the Apple Watch. When you open the message at the watch, you have to option to send a reply directly via the watch. This usually works on all apps (also for apps which does not have a dedicated watch support like Signal, Riot/Element etc.), so this seems to be handled by WatchOS/IOS.
Unfortunately it does not work with Rocket Chat.
Environment Information:
- Rocket.Chat Server Version: 3.10.4
- Rocket.Chat App Version: 4.14.0
- Device Name: iPhone 11 Pro Max / Apple Watch 4
- OS Version: IOS 14.4
Steps to reproduce:
- Receive a message while the iPhone is in sleep mode
- You receive the notification at the Apple Watch
- Open the message at the watch and select "Reply", then select one of the predefined replies
- You get an error message "Failed to reply message"
Expected behavior:
You should send the reply from the Apple Watch
Actual behavior:
Replying from the Apple Watch gives the error message above
Additional context:
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
Start by reproducing the failure using the listed iPhone 11 Pro Max, Apple Watch 4, iOS 14.4, server 3.10.4, and app 4.14.0. Trace the notification's predefined-reply flow from the Apple Watch and identify why it returns "Failed to reply message". Done means a reply sent from the watch reaches the conversation successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100