fix(work): gate FGS mediaProcessing type to API 35+ (Crashlytics 9663c743)#79
Merged
Merged
Conversation
…lback Android 14 rejects FOREGROUND_SERVICE_TYPE_MEDIA_PROCESSING (8192) as an unknown type, fatally crashing every Loopify save (Crashlytics 9663c743). Fall back to dataSync on API 29–34, add regression tests, and OEM sweep tooling to prevent recurrence. Co-authored-by: Cursor <cursoragent@cursor.com>
Ships the Android 14 FGS type fix (Crashlytics 9663c743) to production. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes a 100%-repro fatal crash on every Loopify save on Android 14 (API 34) devices — Crashlytics
9663c743, Galaxy A55 / v1.0.23.Root cause:
BoomerangRenderNotificationspassedFOREGROUND_SERVICE_TYPE_MEDIA_PROCESSING(8192) whenSDK >= API 34, but that FGS type was added in API 35. Android 14 rejects it as an unknown type →InvalidForegroundServiceTypeException→ fatal FGS crash.Fix:
mediaProcessing(correct semantic type)dataSync(WorkManager-documented fallback for long-running export work)FOREGROUND_SERVICE_DATA_SYNCpermission@Config(sdk=[34,35,36]))Closes the production regression affecting all Android 14 users on v1.0.23.
Verification (DoD)
:app:assembleDebug+:app:assembleRelease:app:testDebugUnitTest:app:lintDebugdocs/e2e/2026-06-22_082330-api34-fgs-fix.mdBoomerangRenderWorkerSUCCESS, 0 FGS-type-unknown, SSIM 0.95+connectedDebugAndroidTestE2E proof (API 34)
Version
1.0.24 (versionCode 24) — included in this PR.
Release comfort
Yes — comfortable merging this fix. The root cause is unambiguous, the fallback type is documented by Google for WorkManager long-running workers, and we have automated tests plus real-device validation on both API 34 (emulator) and Samsung hardware (RTL).
Also in this PR (supporting, not user-facing)
DeviceMediaHintsOEM identity tests)drive-flow.ps1— Samsung photo picker skips "Done" step (RTL automation fix)Test plan
mediaProcessingtypeMade with Cursor