- News
- Reviews
- Bikes
- Accessories
- Accessories - misc
- Computer mounts
- Bags
- Bar ends
- Bike bags & cases
- Bottle cages
- Bottles
- Cameras
- Car racks
- Child seats
- Computers
- Glasses
- GPS units
- Helmets
- Lights - front
- Lights - rear
- Lights - sets
- Locks
- Mirrors
- Mudguards
- Racks
- Pumps & CO2 inflators
- Puncture kits
- Reflectives
- Smart watches
- Stands and racks
- Trailers
- Clothing
- Components
- Bar tape & grips
- Bottom brackets
- Brake & gear cables
- Brake & STI levers
- Brake pads & spares
- Brakes
- Cassettes & freewheels
- Chains
- Chainsets & chainrings
- Derailleurs - front
- Derailleurs - rear
- Forks
- Gear levers & shifters
- Groupsets
- Handlebars & extensions
- Headsets
- Hubs
- Inner tubes
- Pedals
- Quick releases & skewers
- Saddles
- Seatposts
- Stems
- Wheels
- Tyres
- Health, fitness and nutrition
- Tools and workshop
- Miscellaneous
- Buyers Guides
- Features
- Forum
- Recommends
- Podcast
Add new comment
3 comments
It has now been fixed![1](https://cdn.road.cc/sites/all/modules/contrib/smiley/packs/smilies/1.gif)
I think it's due to an "undocumented feature not available in the next release"* introduced by a recent update of the Garmin Connect Mobile app. There's a few threads in the Garmin forums about it. I suspect it will go away when Garmin update the app soon.
https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner...
* software bug
Cheers. At least it's not just me - and it seems to have started at the same time for everyone, as you'd expect with a bug in an update.