I know I’m one of the few on software version 10.10 and also iOS 16 (beta 1) so I don’t expect everything to play nice right off the bat with beta software. Just wanted to report what I’ve found so far. Didn’t post this in the beta forum because I know 10.10 was supposed to be a general release before it was delayed. If it needs to be moved to the beta forum, please do so.
Garmin Connect mobile seems to be giving me issues when trying to view “Device Settings” (tapping the watch icon on the top right of the screen). Constantly giving “Error - Unable to load content”. Have tried it on cellular and Wi-Fi, restarting both devices, unpairing device from both Connect and Bluetooth menu, and pairing the device again to no avail. If I shut off Bluetooth on my iOS 16 device and reconnect to another device on iOS 15.4.1, I have no issues viewing this data. I also have zero issues with viewing/changing the watch settings on Garmin Connect Web Version. Everything seems to be working well there. The only thing I haven’t tried yet is reinstalling the iOS16 beta via ipsw. I will try to get around to that if possible over the next few days and see if that corrects the issue.
iOS 16 had also been giving me trouble viewing Garmin weather giving the the never ending “waiting for data”. Same troubleshooting as above as well as starting an activity to obtain GPS, ensuring location was set to “always on”, and making sure background app refresh was turned on with no success. The only way I was able to fix was to reconnect to the device on iOS 15.4.1 and start an activity to obtain GPS. Seems to be working as it should be now even after switching back to the device on iOS 16. Just wanted to post this workaround in case anyone else had the same issue
These seem to be the only two issues that I’ve had arise within Garmin Connect mobile since installing iOS 16. Everything else seems to be working as it should. I’ve had zero issues with my workouts or viewing any other data. If I come across anything else, I will report it also. If anything corrects itself in the next beta release, I will report that as well.
