-
Notifications
You must be signed in to change notification settings - Fork 567
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
SecurityException: Not allowed to bind to service #2062
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @brunoescalona, and thanks for the bug report! We're actively looking into similar reports (internal ref b/168922691) that seem to be affecting that same slice of devices, and this gives us another data point indicating it may be something device-specific. We haven't settled on a solution just yet, but the team has proposed a couple of different ideas and hopefully we'll have something to share here soon. |
Thanks @ciarand! I will wait for the possible solution. |
I noticed the same bug in an application I'm maintaining. So far it only occurred on Wiko View 4 devices running Android 10. |
Hello. We have the same error too. |
Hey @ciarand , are there any updates on this issue? Maybe there is already some plan for a mitigation? Or maybe some way to work around and prevent that crash? This problem is the cause of 50% of all crashes we are seeing within our app. |
Hey @ciarand another 2 weeks passed, any updates? Anything that we could do to fix/work around/debug/help solving this issue? We are counting 50k crashes caused by this problem with our latest release. |
Hi, we are also facing the same issue. |
Hi! @ciarand could you push a bit this issue? Is one of our main crashes right now. |
I also noticed this crash on Cat S42 devices. |
Hello, |
Is there any update on that issue? |
Same for me, crashed on Wiko View4 |
Same issue here. any workaround steps maybe? please update. |
Same issue seen on a HUAWEI ART-L29 running Android 9. |
Same crash on CAT S42 / Android 10 devices. |
Same crash on Cat S42, Android 10 device |
Same crash on 100% TINNO SUGAR T20,,SUGAR T30, Android 10 device |
Wow, I am also seeing this happen to our single CAT S42 Android 10 user in our production app 😮 |
Getting the same crash on LG W31, W11 and LM-K610IM as well. Any update on this issue? |
getting 100% crash on Symphony android 10 devices |
Crashes on Cat S42 and Wiko View4, both Android 10. |
I'm seeing the same crash on WIKO View4 Lite, any updates? |
Not to pile on, but I'm also still seeing this crash - Wiko View4 Lite and Cat S42 devices. |
I have this problem, how to solve it? |
Same here, Wiko and Cat Android 10. |
Have the same issue with the specific device - |
Facing the same issue on Wiko, sad to see there have been no activity or suggestion on this issue |
Same here (with View4 and View4 Lite) We need answers to our customers... WE ALL ENCOUNTER PRODUCTION CRITICAL CRASHES !!! Thanks |
(at least a workaround, or a manner to catch a managedException will be appreciated...) |
Same here on Wiko View4 and View4 Lite. Android 10. |
|
We are facing the same issue in LG W31 model. Any solution or workaround will be appreciated. Thanks Fatal Exception: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms } |
I'm no longer working at Google, but when I left this was on the team's radar. I think maybe @gsakakihara may be able to provide an update on the status of b/168922691 |
We see a huge spike of this crash from yesterday (Android 10, 96% Wiko devices). Any updates here? |
We've added a workaround that should stop it from crashing in version 17.0.0 of the play-services-cloud-messaging library. The next release of the FCM SDK should update to use that version of the library, including the workaround. You could try to add that version of the dependency directly, but I believe since the new version of the library contains a breaking change, you may run into incompatibilities with the current version of the FCM SDK and it may not build. |
@gsakakihara Could you be so kind and clarify which version contains fix? |
Hi @gsakakihara, we are still facing the same issue for LG Devices, W41 & W31 using library 'com.google.firebase:firebase-messaging:20.1.0' |
It hasn't been released yet, but the change should be included in the next release of the library, which is targeted in the next few weeks, barring any issues. |
@gsakakihara Do you mean the version |
Yes, version 23.0.0 should include the workaround. |
Was there any update on this starting from Nov 13? We see a huge drop in number of crashes here, even without the latest library update (firebase-messaging:23.0.0). |
No, there isn't anything that I know of that could be changed remotely from our side that would cause the number of crashes to drop. |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
I am not able to reproduce the issue, mainly WIKO devices are affected by that one.
Relevant Code:
It seems that the Service cannot be bound due to security problems.
I review my manifest permissions and I am including the
com.google.android.c2dm.permission.RECEIVE
permission, needed for thecom.google.android.c2dm.intent.REGISTER
intent.The text was updated successfully, but these errors were encountered: