element-hq / element-hq/element-ios

Not able to copy 3rd and later messages that sent by element-desktop

Open
#7,087 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-Room A-Timeline O-Occasional S-Major T-Defect
Dominant language
Swift
Stars
1.8k
Forks
544
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. I have a DM private encrypted verified room.
2. One persone uses element-ios on iphone and the other person use element-desktop on Windows 10 x64.
3. element-desktop sent 4 messages in this DM private room.
4. element-ios can copy the 1st message and paste it to the input field. As well as 2nd message.
5. element-ios did the copy for the 3rd message but paste as 2nd message in the input field. The copy action has no effect.
6. element ios did the copy for the 4th message but paste as 2nd message in the input field. The copy action has no effect.

### Outcome

#### What did you expect?
In step 5, I should get a copy of 3rd message in the input field.
In step 6, I should get a copy of 4th message in the input field.
#### What happened instead?
As step 5 and step 6.

### Your phone model

iPhone 13 mini

### Operating system version

iOS 16.1.1

### Application version

Element 1.9.10

### Homeserver

Synapse 1.71.0

### Will you send logs?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the copy-and-paste behavior described for the third and fourth messages in a verified encrypted DM, using the stated Element iOS and element-desktop setup where possible. Done means that copying either message pastes that same message into the input field; the report names no source files or tests, so locating the relevant implementation will require project investigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.