Reply text not visible when receiving reply to a message

[ehuelsmann]

Steps to reproduce

I'm doing nothing. Just reading the channel. Others are replying to my message, but I can't see the reply, only the "repetition" of the message replied to. See below. Btw, in the web client I can see that the reply was not actually empty.

Outcome

What did you expect?

I expected to see the most important part of the message: the reply sent by the OP, not just the text of the original message (the one replied to).

What happened instead?

I'm not seeing the text I did expect to see.

Ps: in response to the two questions below: I have sent logs. And I would provide a PR if I knew how to code an Android app.

Your phone model

Motorola g73 5g

Operating system version

Android 14

Application version and app store

From Play Store.

Homeserver

Matrix.org

Will you send logs?

No

Are you willing to provide a PR?

No

[weebl2000]

+1 also experience this since a few weeks.

Workaround for now: If you long press the message you can still read the reply.

[Destroyer]

have this issue too, renders reactions useless for users on mobile (or I have to tell people to long press)

maybe #8947 doesnt work? / was this commit pushed to play store? I am still on 1.6.24

[promasu]

I just tried and downloaded the apk from the latest release on GitHub to upgrade the app. With the new version the rendering issue is resolved.
The devs have to point out why this release hasn't been published to Google Play

[Enoch247]

I am also experiencing this issue.

[rbt2024]

Same here with Android 14 on moto g73 5G / Play Store but there are several friends with different devices with the same bug.

[masscream]

+1 Android 14 / F-Droid release 1.6.24, and also one more device with Android 8....

[promasu]

This issue is a duplicate of #8947. The version with this fix (1.6.26) is so far not available today Google Play thus only available via direct download from GitHub.

[rbt2024]

in Google Play is only version 1.6.24

[ehuelsmann]

@promasu actually, #8947 is a PR, not an issue. I'll agree that this is a duplicate of #8162 .

[ehuelsmann]

Publishing the version with the fix will be really helpful: it's been like this for months now.

[promasu]

@ehuelsmann you are totally right. Grabbed the wrong id :D