Challenge Mode Crashes & Invalid Leaderboard Data

Hi FulGaz team,

I’d like to report two ongoing issues that have been affecting my experience with the app for quite some time.

1. Challenge Mode Crashes Frequently

The “Challenge Mode” feature crashes in roughly 50% of all attempts when I try to select a ride using “Select time to ride against”. I’ve reported this several times already, but unfortunately the issue still persists. I’m hoping that by posting it here, other users experiencing the same problem can upvote it so it gets more visibility.

The crash occurs on two different iPhones as well as on my Apple TV, which is the device I use most often. The app shows the “Please wait” message for about 20–30 seconds and then crashes. On popular rides such as Alpe d’Huez, this feature never works at all.

For context: I never had any issues with Challenge Mode in the older v5.0.x versions — the crashes only started happening with the newer releases.

As a software developer, my guess is that the list of available rides might be generated dynamically on the backend, which could be causing long response times. If that’s the case, a more efficient approach might be to maintain a small index file per ride that gets updated after each upload. The app would then only need to download this file and append the latest ride, which should be significantly faster and more stable.

2. Leaderboards Contain Clearly Invalid Data

Another issue is that many leaderboards are topped by completely unrealistic rides — for example, riders showing sustained 10 W/kg or climbing Alpe d’Huez in 20 minutes. This makes it nearly impossible to place in the top 10 or even top 20 on most rides, because the leading entries are clearly not legitimate.

I would really appreciate it if obviously invalid data could be cleaned up from existing leaderboards, and if some form of validation or plausibility checks could be implemented to prevent such data from being uploaded in the future.