element-hq / element-hq/element-android

Crash while cross-signing with my other Element Web device

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

Description

### Steps to reproduce

1. Initiate a verification request from Element Web on my computer to Element Android on my phone
2. Use the QR Code scanning method to verify the device
3. After scanning the QR code, a spinning process indicator is shown on the phone
4. The app crashes
5. Element Web shows the green checkmark shield

### Outcome

#### What did you expect?

Element Android to not crash, and for verification to succeed.

#### What happened instead?

The app crashed. After reopening Element Android, in Security & Privacy it says:

Cross-Signing is enabled
Keys are trusted.
Private keys are not known

I'm not sure whether the last line is a cause for concern.

The Element Web instance eventually timed out and considered the verification as cancelled.

Edit: I initiated the verification again from Element Web and this time the process went smoothly.

### Your phone model

Google Pixel 4a 5G

### Operating system version

Android 12

### Application version and app store

Element version 1.4.25 [40104252] (G-b9267), Matrix SDK Version 1.4.25 (1f34d368), olm version 3.2.12

### Homeserver

amorgan.xyz

### Will you send logs?

Yes

### Are you willing to provide a PR?

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.