element-hq / element-hq/element-android

broken xsigning state?

Open
#5,030 1 comment 0 reactions 0 assignees View on GitHub
A-E2EE-Cross-Signing O-Occasional S-Major T-Defect X-Needs-Investigation Z-Papercuts
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

### Steps to reproduce

1. log into E android 1.3.15 f-droid
2. ignore the xsync popups
3. go to settings

related: https://github.com/vector-im/element-web/issues/20686

### Outcome

#### What did you expect?
can enable xsign

#### What happened instead?
"Cross-Signing is enabled. Keys are not trusted"

There is only the option "to reset keys". I don't want to ruin my xsigned sessions so I'm not touching that.

#### What then?
1. Press "set up secure backup", verification request appears on desktop
2. Web only says "Verification requested" I think there ought to be a device name in there?
![image](https://user-images.githubusercontent.com/2803622/150645641-594836e5-cc94-416f-a5ed-0c6c75f98952.png)
3. Web is stuck "Accepting"
![image](https://user-images.githubusercontent.com/2803622/150645659-d0744040-4431-4665-ba1a-b7cecf05325f.png)

### Your phone model

_No response_

### Operating system version

10

### Application version and app store

1.3.15 F-Droid

### Homeserver

_No response_

### Will you send logs?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.