element-hq / element-hq/element-x-android

Stuck on login screen, trying to cancel leaves app in unusable state

Open
#1,188 1 comment 0 reactions 0 assignees View on GitHub
A-OIDC O-Uncommon S-Major T-Defect
Dominant language
Kotlin
Stars
2.4k
Forks
624
Avg merge
1d 14h
Merged PRs (30d)
149

Description

### Steps to reproduce

Installed the app and went through the login process.

Network connectivity was decent (4G) and the account is not huge (a few large rooms, but no m.org HQ for instance).

After the OIDC login _per se_ and choosing "allow" at the callback screen, Element X stayed stuck on the cancel/allow/signout screen, with an endless spinner.

None of the button reacted or did anything, so i couldn't cancel log in, couldn't "allow" again, and couldn't sign out.

After a few minutes, i chose to go back using the Android back action, which led to a series of OIDC error messages and left the app in an unusable state, as i could not sign out nor finish signing in ("authorization grant not in a pending state").

I was able to capture some screenshots. They should be in order of how things happened.
![Screenshot_20230829-123239](https://github.com/vector-im/element-x-android/assets/1172256/7613a41a-4715-4b86-bc15-a54927a0a4c4)
![Screenshot_20230829-122605](https://github.com/vector-im/element-x-android/assets/1172256/886c3e5c-4337-4a83-9031-365a4c967486)
![Screenshot_20230829-122618](https://github.com/vector-im/element-x-android/assets/1172256/68c7a8d5-8de4-49df-a64f-344686b6b69c)
![Screenshot_20230829-122623](https://github.com/vector-im/element-x-android/assets/1172256/35381545-d29d-47b9-9a8c-695453798427)

I eventually deleted the app's data, and started from scratch. This time, i didn't get stuck on the cancel/allow/signout page and was able to get my account to sync:
![Screenshot_20230829-123757](https://github.com/vector-im/element-x-android/assets/1172256/8845a321-8e95-4ca4-b327-7fd46be07616)

This took some time, but wasn't worrying as the app was clearly asking me to wait.
I was then finally logged in.

I don't have logs, but i could try to reproduce by wiping app data and logging in again, if requested.

### Outcome

#### What did you expect?
A smooth login process. Information about what the app was doing, if i need to wait.

#### What happened instead?
An endless spinner, unresponsive action buttons and the login process falling apart by both showing behind the scenes info users shouldn't see and leaving the app in a completely unusable state.

### Your phone model

Pixel 2

### Operating system version

GrapheneOS (Android 11)

### Application version and app store

0.1.5 (40001050) from Play Store (via Aurora Store)

### Homeserver

element.io

### Will you send logs?

No

### 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.