-
Notifications
You must be signed in to change notification settings - Fork 21
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
Bluetooth permission was asked during onboarding #1355
Comments
Not high priority for now, moved to 2.3 |
Found it. Its how BTKit is implemented and used on the app. And, I would prefer not to do anything about it since its going to affect the whole BT scanning mechanism across the application. And, the outcome is not also not something significant from all those changes even if we do it. |
Closing this, will be handled in BTKit repository with card ruuvi/BTKit#1 |
Reopened, this issue was not handled due to not being on board. |
fixed in #1925 and ruuvi/BTKit#13 |
The request for permission to bluetooth, even though the instance of station has been running for a while(?) and Bluetooth access is already granted, occurs very rarely. Is there a way to check permission and if (seemly not) check a second time? For me, VERY minor issue but I thought I should let you know. |
@rinat-enikeev 2.6.0 (2402061941) If I open app and leave it untouched on first onboarding for a few minutes I will see permission popup. |
@rinat-enikeev Was the BTKit side fix already done? Can this be then fixed on the app side already? |
It seems that for on boarding station must ask permission once. |
Description:
User made fresh installation of app, then went through onboarding slides
Actual: user was shown Bluetooth permission popup when he was on signin page.
Expected: should ask only when it's necessary
The text was updated successfully, but these errors were encountered: