-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[de.check24.check24] BackgroundServiceStartNotAllowedException: Not allowed to start service Intent #2524
Comments
Hi @ln-12, thanks for your report. Version a) Can you confirm that you see this issue exclusively with Assuming this report is coming from multiple users, I guess we can rule out user specific settings (like blocking the app from running in background via battery settings in the OS). However /e/OS might include privacy related functionality like tracker blockers that block the execution of the analytics service and thereby cause this issue. |
Hey @mar-v-in, thanks for that fast response! a) No, I cannot yet say that for sure. We only got crashes from that version so far, but there might also be other versions affected. The same goes for the time frame. Maybe we were just lucky that it did not show up earlier? b) Shortly before that date, we updated (besides others) I see, thanks for the explanation! |
@ln-12 the above log shows |
Mh, that is strange. When I run I am not that deep into custom ROMs and alternative play service implementations, but could it be possible that our .apk is somehow patched at installation/run time? Or maybe the proguard symbol mapping is not up to date. |
Maybe the stack trace you provided is a report from a user that used a version of Check24 app before the migration to 18.1.0? That would confirm that the issue is not related to the version of play-services-analytics being used. |
Regarding the version discrepancies: It seems that Google repackaged the August 26 somewhat matches the release data of /e/OS 2.3 (which was released August 22). You might want to open an issue at https://gitlab.e.foundation/e/os/backlog/-/issues. It might well be that this crash is invisble to the user and has no negative side effects, as the log claims that starting the service is not allowed because the app is in background. |
That would be a comprehensible explanation. I will do so, but their strict registration policies force me to manually write them an email to set up an account. |
Affected app
Name: CHECK24
Package id: de.check24.check24
Describe the bug
I am a developer of the CHECK24 app. We are getting quite regular Sentry crash logs since 6th August with the error message
Not allowed to start service Intent { act=com.google.android.gms.analytics.ANALYTICS_DISPATCH cmp=de.check24.check24/com.google.android.gms.analytics.AnalyticsService }: app is in background uid UidRecord{db0c2cc u0a241 CAC bg:+4m23s554ms idle change:procadj procs:0 seq(404703,399269)}
. The Google Play version is set to0.3.2.240913-22
which directly leads to microG when searching it in Google. So I assume that it is related to this project.Here is the stack trace:
To Reproduce
We can unfortunately not reproduce this crash locally as it a) seems to be rare and b) we don't have test devices running microG.
Expected behavior
The app should not crash when the user has microG installed instead of the regular Google Play Services.
System
Android Version: we got crash logs for Android 12 and 13
Custom ROM: I cannot see if a user has a custom ROM installed, but the Sentry root detection shows that the devices are not rooted
microG
microG Core version: 0.3.2.240913-22
microG Self-Check results: I cannot verify that as I don't use microG
Additional context
Please let me know if there is something that we can do on our side to prevent this.
The text was updated successfully, but these errors were encountered: