Failure to sync activity data to COROS servers
Activity data synced between 4 AM PST to 10 AM PST on 11/8 may become missing or incorrect on the COROS app or COROS Training Hub. The affected server was suspended at 10 AM PST. This issue no longer affects data syncing for new activities after 10 AM PST.
Our team is working on recovering the affected data. It may take up to a few days to complete the process.
Issue identified on 11/8/2022 at 9:00 AM (PST)
Issue resolved on 11/8/2022 at 10:00 AM (PST)
Upcoming Server Maintenance
We will be performing scheduled maintenance beginning on Thursday, August 18th, at 10:30 PM (PDT). App functions that require cloud communications are not accessible during this window, including but not limited to COROS Training Hub, COROS app data sync, training plans/workouts/routes download, viewing previously completed activities, account login, and password reset.
Please do not uninstall the COROS app to avoid data loss.
Maintenance begins on 8/18/2022 at 10:30 PM (PST)
Issue resolved on 8/19/2022 at 7:00 PM (PST)
VERTIX 2 Satellite/GPS Connection Issue
Starting on July 11th, 2022 we are aware of a problem causing the VERTIX 2 to have trouble connecting to satellites. This issue is caused by the most recent download of satellite data downloaded automatically within the COROS app and leads to long delays while trying to establish a new satellite connection.
Solution: To resolve this issue, please adhere to the following steps.
- Manually update satellite data within the COROS app
a. Navigate to the Device page (4th tab on bottom) and select "GPS Satellite Data"
- Allow extra time before any activity for your VERTIX 2 to connect to satellites
- In 1-3 days satellite data will be automatically refreshed, resolving the issue
If none of the above solutions work, please contact email@example.com, and our team will be more than happy to help.
Issue identified on 7/11/2022
Issue resolved on 7/14/2022
Failure to properly update the satellite location data
We have noticed a widespread issue causing COROS watches to display the soon-to-be-expired satellite location data message despite recent updates on the COROS app. The team is investigating the issue and expects to provide solutions soon.
Watches with expired satellite data may take up to a few minutes to establish GPS connections. It's highly recommended to wait until the GPS is fully connected before starting outdoor workouts.
Solution: Please go to the COROS app > Device page > GPS Satellite Data to manually update the data.
Issue identified on 6/25/2022 at 5:00 PM (PST)
Issue resolved on 6/25/2022 at 7:00 PM (PST)
Failure to connect to GPS and acquire workout heart rate after updating to V2.67
COROS watches that have been updated to V2.67 before 3 am PDT on May 20 may encounter an issue causing GPS connection and workout heart rate failure.
Please contact firstname.lastname@example.org and share your 6-digit watch ID to receive new firmware to download.
Solution: You can also follow the steps below to fix the issue on your own.
- Download a file from this link.
- Connect your watch with a PC/Mac via the charging cable.
- Locate the "Upgrade" folder in the watch drive.
- Copy and paste the downloaded file into the "Upgrade" folder.
- Turn off the Bluetooth on your phone/tablet. (This step is very important)
- Disconnect the watch from the charging cable.
- Wait for the watch to complete the firmware update.
- Test and see if the GPS and heart rate issue is fixed.
All firmware updates completed after 3 am PDT on May 20 aren't affected by this issue.
Issue identified on 5/20/2022 at 3:00 PM (PST)
A temporary solution is provided on 5/20/2022 at 11:30 PM (PST)
COROS app V2.9.29 crashes on iOS 12 or older versions
The latest COROS app (V2.9.29) will crash on iOS 12 or older versions due to compatibility issues.
Solution: Please click here for a temporary solution to revert back to the previous app version and avoid app issues.
V2.9.29 on iOS 13 or newer versions are not affected.
Issue identified 2/11/2022 at 12:30 AM (PST)
Issue resolved 2/17/2022 at 5:35 PM (PST) via V2.9.30 app update
Stryd syncing issue affecting COROS VERTIX 2 watches
COROS VERTIX 2 watches (firmware V2.63 and 2.64) are experiencing issues syncing advanced running metrics from paired Stryd pod or COROS POD 1 to the COROS app and 3rd party apps.
All other workout data is not affected. In addition, real-time advanced running metrics are still available on the watch during training.
Issue identified on 1/24/2022 at 4:00 PM (PST)
Issue resolved on 1/24/2022 at 8:35 PM (PST) via V2.65 firmware update
Strava Routes syncing issue
Strava Routes integration is affected while all other connected platforms and integrations are still working. Our team is investigating this issue and will provide updates once they are available.
In the meantime, please export Routes via GPX format from Strava.com and manually add them to the COROS app
Issue identified on 1/21/2022 at 3:00 PM (PST)
Issue resolved on 1/21/2022 at 5:30 PM (PST)
Data syncing issue with Strava
Data syncing to Strava may be affected while all other connected platforms are still working. Our team is investigating this issue and will provide updates once they are available. Please visit this blog for instructions on manual data import to Strava.
Issue identified on 10/18/2021 5:00 AM (PST)
Issue resolved on 10/26/2021 7:00 AM (PST)
Data syncing issue with Strava
Strava connection including workout uploads and Strava Routes downloads is temporarily affected and nonfunctional. Our team has identified the cause and deployed a fix. All affected data syncing is expected to be completed automatically on 10/17.
All other connected platforms are fully operational.
Issue identified on 10/16/2021 at 5:00 AM (PST)
Issue resolved on 10/16/2021 at 5:00 PM (PST)
Bugs from COROS app V2.6.9 for Android
The V2.6.9 app for Android phones may experience a bug that prevents the COROS app from managing all apps for the notification feature. This version also isn't fully compatible with the Android 12 OS.
Please download the new app update V2.6.15 from this link or Playstore.
Issue identified on 8/25/2021 at 9:00 AM (PST)
Issue resolved on 8/28/2021 at 4:00 AM (PST)
Data syncing issue with Final Surge
Data syncing to Final Surge may be affected while all other connected platforms are still working. Our team is investigating this issue and will provide updates once they are available.
Issue identified on 8/3/2021 at 9:00 AM (PST)
Issue resolved on 8/3/2021 at 11:30 PM (PST)
Data import not working properly
Our team is currently fixing a bug that is preventing the manual import feature from working properly in the user login portal. All new files are affected and won't be accepted. We apologize for any inconvenience caused by this issue and expect to fix this in a timely manner.
Issue identified on 7/12/2021 at 6:00 PM (PST)
Issue resolved on 7/12/2021 at 6:50 PM (PST)
Activity time zone resets to Greenwich Mean Time (GMT) when synced to TrainingPeaks
The time zone of workouts tracked by your COROS devices may be reset to Greenwich Mean Time (GMT) when synced to TrainingPeaks. This affects all workouts synced automatically or manually exported from the COROS app to TrianingPeaks. We are in contact with TrainingPeaks to resolve this issue asap. The issue is likely due to recent changes in API settings from TrainingPeaks.
Data syncing with other supported 3rd party platforms are not affected.
Issue identified on 6/21/2021 at 6:00 PM (PST)
Issue resolved on 6/23/2021 at 12:30 PM (PST)
COROS Server Outage
The server outage is currently affecting data syncing, account login, and customized settings on the COROS app. Workout/daily tracking and other watch functions are not affected. Please don't uninstall the COROS app or reset your watch.
Issue identified on 12/26/2020 at 2:00 PM (PST)
Issue resolved on 12/26/2020 at 3:00 PM (PST)
Elevation/temperature issues affecting COROS PACE 2 watches
Certain COROS PACE 2 (firmware V2.32 and V2.33) watches may experience zero or fluctuated elevation gain during outdoor workouts. Elevation and temperature widgets may remain constant for a long period of time.
Issue identified on 12/22/2020 at 10:00 AM (PST)
Issue resolved on 12/23/2020 at 7:30 PM (PST)