-
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
Constant background Bluetooth time exceeded messages on Series 5 watch #567
Comments
I am experiencing the same and it is VERY ANNOYING. I have a Series 4 and it was working very well. How can I get these messages to stop! |
1.3.2 was submitted to apple yesterday, fixing this. It is STILL awaiting app review... it will release as soon as apple gets their act together and approves the build... |
Funny, I got a notification of this post as I was driving and getting a ton of these. Mine only happened while driving, so far. |
Series 4 watch; waft v1.3.1; M3 v2023.6.11 |
Yeah - they're taking an exceedingly long amount of time to approve this fix. Been 38 hours now... |
FINALLY - app has entered review... should be no more than an hour now... 🤞🤞🤞 |
1.3.2 has been released to the store! Start your update checks! So sorry for the disruption! |
Thanks Kim. |
Im on the latest version of the app, (and watch use to be able to open the door all on its own) however now it appears to be infantility stuck on "connection" when looking at it in the settings I can confirm im on build 1.3.2 build 1274 any trick I need to do after doing the update? |
any updates on this? Just been stuck on connecting ever since the update |
@molster dont see how this is related to the very much solved issue of notifications?! Try removing the watch as key in the vehicle locks menu - and then pair again? |
Following latest upgrade Latest version now generates constant background Bluetooth warning messages. I understand the background stuff doesn’t work on series 5 but previously app was great now it doesn’t work because of the constant nag
The text was updated successfully, but these errors were encountered: