Skip to content
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.

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

Google Pixel App Crashes #875

Open
MattMatt27 opened this issue Jan 12, 2025 · 2 comments
Open

Google Pixel App Crashes #875

MattMatt27 opened this issue Jan 12, 2025 · 2 comments
Assignees
Labels
priority HIGH High priority item QA testing Issue is being QA tested for production release

Comments

@MattMatt27
Copy link
Contributor

Describe the bug
We have seen a sizable increase in mindLAMP crashes for Google Pixel users over the past week

The Error
Looking at the Crashlytics dashboard, the following error appears to be responsible for a bulk of the crashes.

Caused by java.lang.SecurityException
Starting FGS with type health callerApp=ProcessRecord{ab8d26e 11178:digital.lamp.mindlamp/u0a80} targetSDK=34 requires permissions: all of the permissions allOf=true [android.permission.FOREGROUND_SERVICE_HEALTH] any of the permissions allOf=false [android.permission.ACTIVITY_RECOGNITION, android.permission.BODY_SENSORS, android.permission.HIGH_SAMPLING_RATE_SENSORS]

To Fix
We may need to update our AndroidManifest.xml file to make sure it has all the right permissions. I am unsure what Google Pixel or the Android API might have changed recently to cause these new failures.

@sijitg sijitg added the in progress Issue is being worked on actively label Jan 13, 2025
@sijitg
Copy link

sijitg commented Jan 13, 2025

@MattMatt27 We have resolved the issue and submitted an open testing version to Google. However, we are encountering policy issues related to Health Connect permissions that require resolution with Google's review team. Once approved, the fix will be available on the Play Store.

@MattMatt27 MattMatt27 added the priority HIGH High priority item label Jan 24, 2025
@sijitg
Copy link

sijitg commented Feb 3, 2025

This fix is live in the Open Testing (Staging) version 2025.1.30

@sijitg sijitg added QA testing Issue is being QA tested for production release and removed in progress Issue is being worked on actively labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority HIGH High priority item QA testing Issue is being QA tested for production release
Projects
None yet
Development

No branches or pull requests

4 participants