Hi!
I’m wondering if anyone has noticed the following issue on the new IOS update for my TR app on my iPad.
When you finish an interval the summary details (Watts, Cadence, HR) show on top of the text coaching queues meaning I cannot read the coaching queues. Has anyone noticed that?
I feel a bit foolish mentioning this, but I’m sure we all have experienced when you’re tired, little things can sometimes bug you much more than they should!
Had exactly the same experience today.
Recommend taking a screen capture and posting here / sharing with support@trainerroad.com.
The only issue I see is @chad comments are covered by the interval summary.
I had issue with the beeps not working in the old version. I had a support case for it, but we never got to the bottom of it. They work again now.
Yes! That’s what I was experiencing too.
Same thing here. But personally, not a big deal for me.
We’ve had a few comments on this and we’re looking into alternatives. I can’t make any guarantees on if or when this will be changed, but this thread has been shared with the team.
I will note that this overlapping only happens when a device is in landscape mode, so one temporary “solution” is to leave your device in portrait mode - I understand that this may not be possible for everyone. 
Apologies for any frustration or confusion caused!
I’m not aware of any iPad cases that work in portrait.
Related to the new iOS update. I noticed a big jump in battery usage on my iPad. For a 2 hour workout, I usually have over 50% battery life left. Today, I was down to 23%. Has anyone had a similar experience?
The relation is my very first comment.
It’s very slow and laggy on my side.
So it consumes way more power.
So you encounter higher battery usage.
Same to me.
I just want the old version. Can’t use TR anymore. And on smartphone it’s not comfortable.
I need @chad to spur me on after the tough ones 
Hi, all! There are a few too many forum posts about Mobile update issues with the same comprehensive content, so Im merging / closing redundant treads to try to help users find more easily find common threads.
Feel free to defer to the app-specific pages moving forward:
‘New iOS Release Issues / Bug Reports’
‘New Android Release Issues / Bug Reports’
This will help us as a team find common issues more easily, and will also help athletes communicate issues and fixes better with one another. Thanks in advance!
YES. This is so irritating, especially when I’m in the middle of a tough workout and could really use the motivation from @chad. I’ve written in about this about 8 times since the update came out, and each time I get the “we’re aware of the problem, and the dev team is looking into a solution” blowoff.
After 8 months, the sad conclusion is that they don’t care. This is a simple fix – just add the option to turn off the interval summary pop-ups.
We’ve rolled out a few text-issue fixes in recent months! I would check in with support@trainerroad.com so they can look into your app version and devices to make sure we’re clear on what you’re experiencing and that you’re on the latest versions that have those fixes implemented!
I’m 100% on the latest version of the app, version 2021.40.0. And they’re crystal-clear on what I’m experiencing, because I’ve talked to 8 different support reps and sent in screenshots identical to the ones in this thread.
The thing to point out is that I have the iPhone SE (2020 version), which has the 4.7-inch screen, not the 6-inch screen. I’d imagine the others in this thread have the smaller screens as well. Since the majority of people have the bigger phones now, I think TR has decided they can safely ignore the complaints of the minority who don’t have them.
…And no, orienting the phone into Portrait Mode isn’t a solution, because it compresses the data too much.
Making the text smaller just to accommodate us isn’t what I’m asking. But I don’t understand why they can’t just add the option to turn off the interval summary pop-ups entirely, just like we have the option to turn off the instructional text. @Nate_Pearson @chad
I agree this is poor it hasn’t been fixed. It was reported in the beta. It doesn’t reflect well when simple things don’t get fixed.
I know it doesn’t seem the biggest issue, but it is annoying every time it comes up. The rest of the product is top notch, the support is excellent, that just makes it feel worse
Happy to ty and speak better to the time its taken to implement a fix or workaround. The development team has written up an issue for this to address it, however, fixes like these are simply taking a back seat while the team works on high priority issues (such as incorporating unstructured rides into Adaptive Training and refining Adaptive Training as a whole).
While some of these fixes seem small or easy, they can often open up a new can of worms for the development team and prove to be more complex than initially estimated.
That said, it’s not that the team doesn’t think this is an important fix, we just have to prioritize updates that are the most effective at helping the greatest number of athletes possible get faster in the immediate future. Sorry it’s taken so long and thanks for your patience!
Echoing what @bazcurtis said, the rest of the TR app is great, and this ironically makes the problem more frustrating, since we’re not able to fully enjoy it. I think anyone here can relate to the fact that when you’re really suffering on a workout, and you need to muster 100% of your focus toward the task at had, seemingly small annoyances like this can throw you off your game. And again, most of @chad 's instructions during those peak efforts aren’t technical – they’re motivational! And with this problem, not only are we unable to benefit from his encouragement, we’re getting PO’d at exactly the moment when maintaining a positive focus is paramount.
The upbeat and ever-understanding replies of the TR staff are appreciated. But frankly, they only go so far. After nearly a year of the problem not being fixed, the assurances that it will be “eventually” ring hollow.
Any news on this getting fixed. It is over two years now and considering all the other things that have been released I would have thought correcting this issue might have been one of the simpler fixes.
