@Mff73 said in [BUG] Alternative old/new trails are shown in Suunto App route editor depending on the map zoom level: Probably a map caching issue. Maybe try delete app cache and check again? Potentially uninstall / reinstall. These trails changed 4 years ago. I haven’t had my devices for so long. Also, deleting the cache didn’t help. [image: 1759761213654-screenshot-2025-10-06-at-7.32.25-am.png]

@gogapo update: there are more translations issues as you can see in the link I provided. If I change it to English it works fine

@Tieutieu said in Suunto app crashes when filtering summery by tags: I have also reported it several times through beta app (, iOS 24.00 sa version) On my phone (iOS) it crashes so after I tried to filtrered I can’t enter the main menu of the app (recap/activity…) and I also needed to reinstall the app. On my MacBook Pro, reinstalling the app even didn’t solved => app keeps crashing every time I try to access to the menu. [image: 1734414791180-img_3606.jpeg] Update the app to the latest version. If poosible, the best option is Delete the current app and reinstall its latest version. Now, try filtering single tag instead of multiple tags.

@Tieutieu problem solved thanks

Sounds like this might become possible in iOS 26.1 https://www.macrumors.com/2025/09/23/iphones-third-party-smartwatch-features/

@dankcushions ok so it would not require a watch update but an app/api update. This is probably a good news, hopefully they can fond out how to fix it… Thx for tout insight

Why would they remove the search bar, why press on your profile and then activites… so annoying. I also miss the “overview” tab, that was really good. They shouldent have removed it.

@Antonello85 that is just an estimate, that is overrule by the app when you sync. If it does not happen for you it may be an iOS issue indeed (there are no problems for me with Android)

This is an old tread but this continues being an issue. Today’s example: Route ascent/descent when planned in Suunto app: 9200+ ft. The same route ascent/descent when planned in Strava : 7426 ft Actual ascent/descent measured by Race: 7477 ft. The same route ascent/descent measured by Garmin Epix and Fenix 7: 7800 ft. This is way off! Most of the time Suunto App underestimates elevation by 10-20%, but I find that in large mountains it seems to overestimate, especially, I suspect, when traversal of steep slopes is involved. At the same time, Strava is pretty much spot on. Too bad, when a route is synced from Strava to Suunto app, the revelation data is overridden by Suunto app.

@Stefano-M64 Agree, I dont know who removed digits from the app.

@soisan Thanks, everyone. Sorry for not noticing the previous posts - I only checked the iOS subsection of the Forum before posting. Hopefully, my post we be helpful to future iOS users who are also experiencing this issue I can confirm my latest run was classified as “Anaerobic” and not “VO2Max” anymore. While I still think this is a bit exaggerated given my HR zones, it will do. In conclusion, for any future reader: Check your HR zones Check whether you have running-specific HR zones set Check your power zones Check your pace zones I still find it a bit funny that the watch uses Power data to label the running sessions. Where does this data even come from? And setting the zones is also weird, I don’t know what those Power levels correspond to. It would be nice if the watch automatically matched Power/HR zones based on previous activities.

@zucchero you can’t invert pages…you need to be careful when you create (it’s an annoying point of sport mode customization since beginning)

We had some issues which are solved now