Closed baole closed 1 year ago
@baole it was fixed in version 2.21.5 https://tokbox.com/developer/sdks/android/release-notes.html
@DanielGalarza
Is there a particular reason that the BLUETOOTH_CONNECT permission is required, even there is no bluetooth device is connected? In the UX perspective, it's really strange to ask the permission for devices that doesn't have a bluetooth headset.
@baole, the permissions were added because they're mandatory for Android 12+. We had to include them in our SDK to provide better bluetooth experience.
Hope that helps.
@v-kpheng
We understand Android requires this, but the issue was opened because the OpenTok SDK could/should function even if this permission is not granted. Let them users have bad bluetooth experience if the permission is not granted.
Also, it's a little bit confusing that the documentation says this permission is required, but if the user does not grant it (at runtime) I can still have a normal video call. Could you clearly say in the documentation when should we absolutely request this permission to avoid error? From the start even if no bluetooth device is used?
After update our app's target to API level 31, we get a crash from OpenTok SDK because of missing BLUETOOTH_CONNECT
This is because the recent changes in API level 31 as described here: https://developer.android.com/guide/topics/connectivity/bluetooth/permissions
We expect OpenTok SDK handles the case where android.permission.BLUETOOTH_CONNECT is not granted by user instead of crashes