element-hq / element-hq/element-android

Element crashes if obtaining fonts from Google Play Services fails

Open
#3,978 0 comments 0 reactions 0 assignees View on GitHub
T-Defect
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

### Steps to reproduce

1. Install and sign into Element
2. Somehow crash Google Play Services before (See "What happened" for how this was found).
3. Element will crash as it cannot obtain fonts from Google Play Services

### What happened?

This issue was originally found when a user, using the sandboxed Google Play Services on GrapheneOS, attempted to use Element whilst the INTERNET permission was revoked from Google Play Services. This configuration causes Google Play Services to chain crash (as it checks to see if it has the INTERNET permission and will crash if it does not), and so when Element fetches fonts from it, it crashes in this scenario. I was only able to get heavily redacted logs from the user which showed the below happening to the Element following Google Play Services crashing.

```09-07 18:52:18.749 1000 1135 4077 I ActivityManager: Killing 31200:im.vector.app/u0a166 (adj 0): depends on provider com.google.android.gms/.fonts.provider.FontsProvider in dying proc com.google.android.gms.persistent (adj 0)```

### Your phone model

Pixel 5a

### Operating system version

GrapheneOS RD2A.210605.007.2021090401

### Application version and app store

Element 1.2.0 from F-Droid

### Homeserver

_No response_

### Have you submitted a rageshake?

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.