anyone can advice me please, i trying to change setting on the Watchface that i load from Connect IQ, but when i hit Save button, it show message " Open outside Garmin Connect ?"
Short of using a mac/pc - none yet. I'd suggest social media and tweeting etc to Garmin. This serious bug is over a week old and should never have passed basic QC
The problems seems to be with the "Data Fields" settings, as well, can't save any of the settings on any data fields, IOS 12.14 Hey Garmin guys any fix for this?
Same issue. Having troubles with saving changes made to watch faces or widgets. Any ideas how to fix this? Garmin Connect version 4.15.1.2 (iOS) fenix 5X Plus 6.0
my advice... Wait! It's very likely that it's their server but garmin won't publicly publish this... I suspect this is related to their servers. When saving a setting, it's like the server doesn't know you're already on the app and prompts to complete the change via the app.
Since my last sync on February 11th, if my watch sync through garmin mobile connect, my rides wouldn't sync with strava. Going through pc and garmin express worked!
Un pairing with phone, resetting my watch just made it worst. It was only this morning that i was able to pair it back with the app. NOTHING CHANGED on my end.
Through garmin connect, you can see through the logs that the app is unable to connect to server.
error detail: Error domain=GCMsyncerrordomain...
Notice the "GCM" as in Garmin Connect Mobile ????
So yeah... Either go through express or wait 'till garmin man up and confess their servers for garmin connect mobile crapped.
They have narrowed down that it is a mismatch in the iOS language and the detected Garmin language. Users with iOS set to UK English are frequent reporters of the issue. There are some reports that changing the iOS language can provide a workaround but I am waiting for the fix. I am getting by using Garmin Express on my PC for the few occasions that I need to change the setting on my watch. I typically only do this to change the target pace in Peter DeDecker's Race Pacer app.
I initially reported the issue to him thinking it was an issue with his app but it rapidly became clear that it is impacting multiple applications from multiple developers. Peter raised it in the developers area of the forums which meant that Garmin picked it up and we have clear acceptance by Garmin that it is their issue to fix.
For those who are getting impatient regarding a fix, I understand the frustration. I am checking for an update daily but I can also recognise that Garmin would want to do a lot more regression testing on any fix and this will take longer. We should be pleased that they are doing so and hope that this becomes part of their standard procedure to trap this type of error in the future.
