Skip to content

fix(mobile): Android usage widget no longer sticks on "Loading widget" in release builds #15142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maria-rcks merged 1 commit into from
Oct 4, 2026
Merged

fix(mobile): Android usage widget no longer sticks on "Loading widget" in release builds #15142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion apps/mobile/app.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -418,7 +418,16 @@ const config: ExpoConfig = {
minSdkVersion: 24,
// kotlinx-io uses Kotlin 2.3's return-value checker annotation, while
// SDK 58 builds with Kotlin 2.2. It has no runtime behavior.
extraProguardRules: "-dontwarn kotlin.MustUseReturnValues",
//
// WorkManager 2.9 keeps InputMerger classes but not their constructors,
// and R8 full mode no longer keeps a default constructor implicitly.
// Without it no work request can start, so the Glance session behind
// the widget never renders and it stays on "Loading widget". WorkManager
// 2.10 ships this rule itself; drop it once the resolved version gets there.
extraProguardRules: [
"-dontwarn kotlin.MustUseReturnValues",
"-keep class * extends androidx.work.InputMerger { <init>(); }",
].join("\n"),
},
ios: {
deploymentTarget: "18.0",
Expand Down
Loading