-
Notifications
You must be signed in to change notification settings - Fork 38
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
Commission timeout due to AppCommissioningService.onCommissioningRequested not being called #213
Comments
There is a workaround for this issue that consist on launching the service as a ForegroundService. This way the issue is gone for good and the commissioning process can continue. My guess is that this is an issue that affects that particular device (and maybe others from the same brand) due how the Services restrictions are implemented. |
Same issue, my code can be suspended at any time in the progress of the commission step. |
Hi, I'm also having the same problem. |
@franmontiel |
Thanks all for the prompt inputs and workarounds, we are now under investigation about Google Home Mobile SDK. |
I am experiencing this problem with a Samsung A33 5G (Android 14) but I am not able to reproduce it with other devices.
The problem is that after the System Fabric is successfully commissioned
onCommissioningRequested
is not called so the Google Home Matter lib timeout kicks-in (sometimes it is called prior that but it can also take a lot of time and it is not the usual behavior).When I go back to the app from the Google Home Matter UI then suddenly
onCommissioningRequested
is called, but the UI already is gone so the user experience a failure even though the commissioning can still work.Could this be some kind of problem with binding the Service? Could it be that Service somehow being treated as if the app is in background and that's why the method is called once I'm back from the Google Home Matter lib UI?
Any suggestion on what to do? Possible workaround for this?
Here the error when the timeout kicks-in prior
onCommissioningRequested
is calledThe text was updated successfully, but these errors were encountered: