-
Notifications
You must be signed in to change notification settings - Fork 603
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
startNotification not returning any result for API level 33 (Pixel devices) #1010
Comments
The Call History prompt something Android does itself as part of the bonding process. A reasonable overview of this process is recorded here: https://medium.com/@futail2a/why-android-requests-contacts-and-call-history-during-ble-pairing-deb2032c64f5 A few questions:
This is unlikely to be anything related to this plugin however, as what you're running into is native Android behaviour that they don't expose APIs to control. |
Thanks @peitschie for prompt response. Here is answer for your queries.
I think the broadcast listener is not triggering any even for intent to send data back to callback function. |
I have app which is running fine on 80% of devices but Google Pixel devices and Nokia devices (either Android 12 or 13 or 14), when
connect
is called, it is asking for Call History permission which is triggering Negative image for the app to the end users.Also, The
startNotification
function doesn't provide any response and do nothing on these devices. The function neither returning error no returning Success callback.Let me know can be done to avoid this Extra permission message and why I am not getting anything for
startNotification
function.The text was updated successfully, but these errors were encountered: