App crashing iOS for some strange reason

I’ve been having ongoing issues with my app “crashing” during workouts since I switched to iOS. The app seems to be still running in the background as my power still displays, but heart rate drops momentarily once I re-open and continue my workout. It’s not a huge deal since I’m running a dumb trainer setup on a spin bike, but it’s annoying and momentarily takes me out of my zone.

I’m running iOS 17.7 on an iPhone 13 Pro. I have uninstalled and reinstalled the trainer day app a couple of times now with no success. Any ideas on how to solve this issue?

Ok I see the issue you are facing in our logs and a few other people have gotten that error as well. It says “Attempted to dereference garbage pointer at 0x8000000000000010” What heart rate monitor are you using? Also when you say crash you really mean crash, it’s sounds like you are saying loses connection to HR is what happens, correct? And app running in background but power displays, how can you see the power if the app is in the background? I am just confused by your terminology here.

Hi Alex, thanks for getting back to me so quick.
My heart rate monitor is a Polar OH1. What’s happening is the app will crash, and go to my phones home screen. Usually I’m able to reopen the app fairly quickly and not continue. When I get back to my ride it shows a drop in connection to the heart rate monitor, but the connection to the bike through the power data shows no drop. This is where I figure the app isn’t completely crashing, but maybe it’s just establishing connection immediately.

I just reviewed my last handful of rides and noticed they are showing the power numbers dropping while heart rate is continuous which is strange since this is the opposite I see in real time.

I’ve been using the same heart rate monitor and spin bike for the last year with no issues on Android, the problem only appeared when I switched to iOS. Hopefully this all makes sense, I’m a big fan of the app and would like to continue using it.

Ok strange. I would try uninstall>restart phone>reinstall and let me know if it keeps happening I will ask my developer if he has any idea how that could happen.

So far so good, just got through a 60 min recovery ride without issue. Thanks Alex.

1 Like

Success was short lived, back to same issue from the original post the last couple rides. It must be conflicting with something running in the background on my phone, I seem to have more success when I shut everything else down. If I find the culprit I’ll share my findings.

Ok thanks for the update, I also have my developer looking at your error. It’s some strange memory issue but affects a very small number of people.