@kamarasm you could try opening a GPX you know loads in a plain text editor (notepad on Windows) and then open the one that will not load. You will see simple coding, just see if there is any obvious difference or special characters. I used to have to do this on every upload from a Garmin Etrex to have Strava read the elevation from the GPS. Or upload to GPX editor or similar, add elevation then redownload. GPX editor (or why others editors) will rewrite the GPX header.

@jariusxd said in Sync/find my phone: …I need the Suunto app open in order … to use the find my phone from the watch? That one is deliberate.

@pavel-samokha Thx for all your Information

@Efejota yes, specifically for Spain there are places where this version produced poor elevation profile which affected Climb Guidance results n etc. Anyway hope we get back to this later.

@Brad_Olwin I’m sleeping whole day then as my phone is almost whole day laying on desk

@Egika see, you can’t trust anyone - always need to ask @the_ultraman I think the issue for Android should be fixed in the next release

I do agree. Very slow creating routes, much slower than before. I have tried to create a 300 kms route using roads and it simply created a direct patch (even though creating it every 25 kms or so the road route is properly generated). See also this thread: https://forum.suunto.com/topic/12023/problems-planning-long-routes/12. J

@Egika no I don’t use a bike pod

@Max0611 whenever this happens, there is some different account in use. Even if you are 100% sure right now that you are logging in with the same credentials, please triple check. maybe you logged in using your Apple ID, or Google account etc. There has never been a case where data was lost on the backend. Only users accidentally logging in with a different account…

@sc_manning Mine works well, make sure notifications are allowed in the watch/app and the BT stack on the iPhone… To see notifications on the watch they must appear on your lock screen.

Hello Ladies and Gentlemen, i have the same problem since the very start of ZoneSense: Suunto vertical, brandnew Suunto Cheststrab, and this is a typical result after an hour and 8 kilometers. Does anybody have an advise? Thank you and have a nice sunday evening [image: 1730026807842-img_4136.jpg] [image: 1730026807948-img_4138.png]

@iterumtenta Same here! Syncing before Watch ends Sleep recording is messing up the data in the app at least on iOS

@nathant said in ZoneSense not appearing in iOS app: I’m not seeing ZoneSense for any activities recorded on other devices and synced through RunGap, i don’t know rungap, nor iOS, but on the Suunto’s side i may experienced myself, outside Suunto activities are not uploaded in Suunto with full data management. HR data are “just” Hearth Rate ones, and probably not IBI ones (RR/HRV) I didn’t check recently, but you can try : export a nice suunto activity fit file, with all data, zonesense working, etc… Reimport it without any change into Suunto with Rungap, you may loose something not a criticizm, Suunto is having its own devices and manage its own data, and then, when it comes to outside activities, it is managing according to priorities, i think. Even if fit files are well structured, i imagine that so many data “format”/“issues” could not be compliant, and thus a nightmare to manage. Just my own user experience and thinking. [edit] original file for activities imported from outside are stored in Suunto’s backend, as far as i know and see. Meaning, original data are there somewhere

I think I solved it myself. In IOS18 you can lock Apps and I did exactly that with WhatsApp. That’s why new messages would not show up on my Suunto Race. Let’s see what happens tomorrow when the first messages drop in…

I was experiencing exactly this for months. I was not able to setup and/or install some apps, always crashing. I was going mad with it. As an iOS software developer, I know how difficult it is an app to crash nowadays. I was wondering why no-one else were mentioning this issues. Was this a “just me” problem? Then, I decided to delete the app and install again. It solved the issues. My gut feeling is that somehow I ended up having inconsistent or corrupted data somewhere (local db, filesystem, some kind of cache) meaning syncing was not working properly. Delete and install again wipes out the local storage.