New user here - love the app and interface. I recently started using TrainerDay with my Schwinn IC4, but it crashes (12 X in last 30 min ride). It just quits, I reopen over and over. I have uninstalled, rebooted iPad and then reinstalled but the problem persists. I am using an iPad Pro 11-inch M4 with iOS 18.3.1.
Strange. No one else has issues like this that I have heard of. I will have my developers look at the logs to see if they can find the problem and let you know in the next couple days. I know we have other IC4 users so that should not be the problem.
Some things to try
You could try registering for a new account and just see if it happens on the free version to make sure it’s not something strange with your data.
For now you could use a phone assuming it is issue with M4
We should be able to get this fixed fairly soon if we find the problem. If you purchased from Apple you might want to ask for a refund. It’s cheaper from us and I can’t do much to extend your contract for example if you bought from them. If you bought from us we can figure something out.
I was unable to try the suggestions until this afternoon.
russfg is my paid profile
ipad M4 crashes
iphone 16 Pro Max - crashes also
I created russfg01 - as free profile
ipad M4 - no crash
iphone - didn’t check since above worked
Maybe related - i noticed when looking at my russfg profile, the
User account info, in the iPad app it says I weight 504.9 lbs (LOL), when I type my actually weight in the field - the app will pop a ridiculous value instead of what I typed. It is set up to access this data from Apple Health and is fine on the website.
The only app connected to my account is rungap, also my weight don’t change and its without a comma.
So I don’t think that’s the issue.
Today it also happened in Slope mode, at the end of my workout I did a short push, no change in elevation.
And it happened exactly when the interval ended, aka the same as in ERG mode, where it happens at every interval change.
The funny thing is, when I went back to the app/workout, the time was still running, after the workout should have finished, and the interval was counting down from start again.
I finished the workout (pressed stop), and the workout time only showed the original planned workout time, aka not the extra 5-6 seconds because of the failure.
Edit 11 of March:
I reinstalled the app.
Today pure Z2 in Slope mode, no failure.
Hi Alex,
I’ve just tried to perform a workout. Wahoo Kickr Snap, iPhone 15 Pro.
As others are reporting the app crashes when power changes
I’ve had no problems previously, but I have updated both Trainer Day and Wahoo apps since last session.
Hope your folks can sort it as it’s unrideable like this.
Many thanks
We will for sure fix it. The question is how fast… It’s really a strange one since we have many thousands of people recording workouts weekly yet only a couple seem to be affected by this. I am sure it is our bug and we consider it top priority because losing workouts is the worst. Or wondering about losing is pretty bad too.
I pointed AI to this post and asked for suggestions. The only thing it suggested that was new was the following:
Reset Permissions and Clear Data
Action: Go to Settings > General > iPad Storage > TrainerDay, offload the app (to preserve data), then reinstall it. After reinstalling, check Settings > TrainerDay to ensure all permissions (e.g., Bluetooth) are enabled correctly.
Why: Reinstalling alone might not reset all settings or clear corrupted cache. This ensures a fresh start while verifying necessary permissions.
After trying this, I tried a 30 min recover ride to test and had no crashes until about 17 min in, then 3 more crashes in the remaining time. I thought this fixed it but it did improve. Not sure if this points to a memory leak in the app, but it is more data for you. You can see the app crashing in the chart of my workout where the power drops out while I reopen app and resume workout.
I have an apple watch, but I do not connect it to TrainderDay iPad app or even see it as an option.
Not sure if this is helpful but I found the following logs for TrainerDay dated today - but I am unable to attach them they are .ips - I changed them to .gif temporally but even though that is allowed to upload it didn’t like my files. If there is a support email address, i will gladly email them.
Some additional sleuthing I pulled 4 logs from today for Trainer day on the iPAD - I am not sure if there is any useful info but they are attached.
Crash Logs: For advanced troubleshooting, check Settings > Privacy > Analytics & Improvements > Analytics Data for logs mentioning “TrainerDay”
Edit: in addition I was able to attach iPad to Mac and run the console in Xcode to capture the crash log. I just sent that via email. AI (grok) has the following take on the log:
Thank you for providing the crash log for the TrainerDay app on your iPad Pro M4 running iOS 18.3.2. As Grok 3, built by xAI, I’ve analyzed the log to identify the likely cause of the crash and will recommend steps to resolve or mitigate the issue. Let’s break it down step by step.
Crash Log Analysis
Key Details
Incident Date/Time: March 13, 2025, 13:40:34 -0500 (during or after your 30-minute ride).
Device: iPad16,3 (iPad Pro 11-inch M4).
OS Version: iOS 18.3.2.
App Version: TrainerDay 5.2.2.
Exception Type: EXC_BAD_ACCESS (SIGSEGV) with subtype KERN_INVALID_ADDRESS at address 0x8000000000000010.
Termination Reason: SIGNAL 11 Segmentation fault: 11.
Triggered by Thread: Thread 0 (main thread, com.apple.main-thread).
Crash Context: Occurred while interacting with CoreBluetooth, likely during Bluetooth communication with your Schwinn IC4 bike.
Exception Breakdown
EXC_BAD_ACCESS (SIGSEGV): This indicates the app attempted to access an invalid memory address, typically due to a pointer issue (e.g., dereferencing a null or freed pointer).
KERN_INVALID_ADDRESS: The specific address 0x8000000000000010 suggests a possible pointer authentication failure, a security feature in ARM64e architectures like the M4 chip. This could mean the app mishandled a signed pointer, leading to a crash.
Thread 0 Call Stack:
The crash originates in TrainerDay (frames 0 and 1), followed by CoreBluetooth frames (2-6).
Key frame: -[CBPeripheral handleCharacteristicEvent:characteristicSelector:delegateSelector:delegateFlag:] (frame 3) indicates the crash happened during a Bluetooth characteristic event, likely when processing data from your bike.
Likely Cause
The crash is most likely due to a bug in TrainerDay’s handling of Bluetooth data from the Schwinn IC4. Specifically:
Pointer Issue: The app may be accessing an invalid or improperly authenticated pointer when processing Bluetooth characteristic updates (e.g., power, cadence, or heart rate data).
Compatibility Problem: The M4 chip’s ARM64e architecture and iOS 18.3.2’s enhanced security (pointer authentication) might expose a flaw in TrainerDay 5.2.2 that wasn’t evident on older hardware or iOS versions.
Bluetooth Overload: The frequent crashes (12 times in 30 minutes initially, 4 times in this log’s context) suggest the app struggles to keep up with real-time Bluetooth data, possibly due to a memory leak or unhandled edge case.
The call stack’s involvement of CoreBluetooth points to the interaction with your bike as the trigger, aligning with your ride chart showing crashes during active use.
Recommendations for Resolution
Immediate Workarounds
Reduce Bluetooth Load
Action: Disconnect other Bluetooth devices (e.g., heart rate monitors) and ensure only the Schwinn IC4 is connected. Test a ride to see if crashes decrease.
Why: Limiting data streams might reduce the strain on the app’s Bluetooth handling.
Lower Workout Intensity
Action: Try a simpler workout (e.g., a flat ride with no intervals) for 20-30 minutes.
Why: This could avoid triggering the bug if it’s tied to rapid data changes (e.g., during ramps or intervals).
Update or Revert iOS/App
Action: Check for a TrainerDay update in the App Store. If none, consider backing up your iPad and testing a rollback to iOS 18.2 (if available via backup).
Why: A newer app version might fix the bug, or an older iOS might bypass the pointer authentication issue.
Long-Term Solutions
Provide Crash Log to TrainerDay Support
Action: Email the full log (as shared here, with personal data redacted if needed) to TrainerDay support via their website or forum. Include:
Device: iPad Pro 11-inch M4.
iOS: 18.3.2.
App Version: 5.2.2.
Crash Pattern: First at ~17 minutes, then every 3-4 minutes.
Ride Context: Attached chart showing drops.
Why: The developers can use the EXC_BAD_ACCESS and CoreBluetooth stack trace to identify and patch the pointer or Bluetooth handling bug.
Monitor with Xcode (Optional)
Action: Connect your iPad to a Mac with Xcode, reproduce the crash, and export the live log from Window > Devices and Simulators > View Device Logs. Share this with support.
The bug likely lies in TrainerDay’s code where it processes Bluetooth characteristic events. The developers should:
Validate pointers before dereferencing.
Ensure compatibility with ARM64e pointer authentication.
Optimize Bluetooth event handling to prevent memory overruns.
Conclusion
The crash stems from a pointer authentication failure in TrainerDay 5.2.2 while handling Bluetooth data, possibly exacerbated by the M4 chip and iOS 18.3.2. Start with workarounds like reducing Bluetooth devices or workout complexity, then escalate to TrainerDay support with this log. They’re the best positioned to fix this, especially given the hardware-specific nature of the issue.
Let me know if you try these steps or get a response from support—I can refine the advice further!
I had this exact problem yesterday. Every time the interval power changed on ERG mode the app crashed. Happened at least 15 times during the workout. I’m using an older iPad Pro 12.1 and a Tacx trainer.