Bug Reports for the new Desktop App

One more thing came to my mind, which is connected to the onboarding splash screen: I think right now the assumption every TR app seems to make is that it is used by itself. So the Mac app expects that you pair sensors to it, for example. But on the other hand, many users will have many TR-capable devices, and perhaps you prefer to use one for training and another for analysis. In my case I donā€˜t plan on ever pairing my power meter to my Mac, because even right now, my iPhone and my iPad are fighting for it. (Sometimes I have to disable Bluetooth on my iPhone so that TR on my iPad can connect to my power meter.) With a third device, things would only get more difficult.

Sorry if this has been discussed already, but I’m not getting a workout image being displayed over on Strava. Had this ongoing for a few weeks now

Not sure if this has been covered yet. Yesterday was the first ride with the new desktop app. Everything worked ok except the calibration for the Elite Direto, it wanted me to spin up to 239.5km. How is that even possible? I didn’t trust the calibration so 10min in I used the Elite app to do a spindown. It would be nice to finally use Trainer Road to do the calibration instead of using another app.

Thanks
Stephan

We try to make data-driven business decisions. :slight_smile:

As of right now, since the website has more complete analytics tools, I would recommend sticking to the website for analysis. As the apps become more feature-complete with analytics, this is definitely something we’ll have to take into consideration.

1 Like

Strava had made some changes to their OAuth permissions. Try un-syncing and re-syncing your TR and Strava accounts here: Log In to TrainerRoad

Reauthorizing TR access on Strava should fix the issue. Might be some useful info here, too: https://support.strava.com/hc/en-us/articles/360026258271-TrainerRoad-and-Strava

Direto calibration should only be supported when the trainer is paired via Bluetooth. If you’re trying to calibrate while paired via ANT+, you might run into some issues. We’re planning on removing calibration when paired via ANT+ altogether.

  • Platform: Windows
  • Version: 2019.27.0.4
  • Devices: KICKR Snap / Vector 3
  • Connection: ANT+
  • Mode: ERG

Bug:
If a workout is scheduled but not completed and an unrelated outdoor ride has already been completed, the workout will be automatically associated with the already completed outdoor ride and marked as complete when viewing the outdoor version from within the desktop application. Once this happens, there isn’t a native way to ā€œunlinkā€ the two without visiting the web interface.

Example:
I had commuted to work this morning, and planned an indoor workout around my lunch break. I wanted to check out the outdoor version to see if I’d rather go in the heat after work, but the workout was automatically associated with my morning commute and marked as complete when I clicked ā€œOutsideā€. I had to navigate to the web version of the calendar to reverse this automatic change.

Not sure if it’s intended behavior or not, but I don’t believe it should be.

1 Like

That’s odd - I don’t think this is necessarily a bug with the new desktop app itself. All of the automatic association happens on the web-side of things. That said, I don’t believe an outside ride that you complete should ever automatically associate with a scheduled indoor ride. So there very well may be a bug on the website.

For your second point about ā€˜unlinking’ or disassociating the indoor from the outdoor ride, you should be able to do that in the app by hovering over ā€˜Change Association’ and selecting the option here:

Was this not available for you in the app?

1 Like

The association is in the app, I just missed it in the UI. Thanks for pointing it out to me and the rest of the community!

Is there another place I should report the automatic association?

I think we have an issue open that is similar to what you reported - I’ll add your report to that open issue. Thanks for letting us know, though!

1 Like
  • Platform: Windows
  • Version: 2019.27.0.4 (Stable release channel)
  • Devices: KICKR 2016 / 4iiii Precision Pro / Garmin HRM
  • Connection: ANT+
  • Mode: ERG

Bug 1:
On startup, the app is fullscreen which covers the taskbar. If i click the Maximize/Restore button to resize the window, the taskbar comes back into view. If I try to drag the top of the window down to resize, the window disappears to the taskbar. Only way to get this back is to restart the TR application.

Bug 2:
When in Minimal Mode, the application appears to be partially covered by the taskbar when first switched to Minimal Mode. However, when the window is fully minimized to the taskbar and restored, it appears scooted up with a lot of blank space beneath that didn’t previously appear.

Bug 3:
At times the calendar won’t refresh properly and appears blank. Application must be restarted to correct.

Video:
Here’s a video demonstrating these issues: - YouTube

So The green highlight at the top of the TR app suggested to me this morning (July 9, 2019) that I should restart the app on my PC laptop to update the software. The updated TR software is really slow compared to the version before the update. The new TR on my PC took about 15+minutes to load my previous workouts and the calendar. On the initial start of the software I could not even move its window to my other monitor, so I had to force a shutdown and relaunch it. The new interface design looks nice, but I would rather have an effective application instead of better aesthetics

That particular step is a one time process needed to setup the revised app. It will not repeat once allowed to complete. Subsequent loads will be ā€œnormalā€ speed and much faster than that first launch.

1 Like

Thanks for the video! The visual representation helps a lot.

Regarding Bug 1 and 2, we have open issues to handle the taskbar a little bit better. In minimal mode and full-screen. I’m not sure exactly how we’re going to do that. Some people have the taskbar hidden by default, or will want to access it during a workout. I’m sure there’s a solution, we’ll get there.

As for Bug 3, we also have some open issues for this one. Calendar has been super tricky to get it to ā€œplay nicelyā€ and always load perfectly. When it goes blank, you should be able to click ā€˜Today’ in order to get it back. I don’t think you always need to restart the app.

Really appreciate the report!

Is there any ETA on fixes for the resizing/taskbar issues? Is the updated version @Geoff posted about back on June 6th (version 2019.23.3.36) not supposed to fix the application resize issue as indicated by his ā€œfixesā€?

I purposely held off on beta testing the application, because I wanted a mature application without these kinds of bugs. It took all of 30 seconds to identify (and be annoyed by) these issues. At this point, it feels to me like an application still in beta that I was automatically ā€œupgradedā€ to.

Hi there! :slight_smile:

Thanks for your feedback and I would like to apologize for any frustration you’ve encountered as a result of this. Feedback has been overwhelmingly positive for our new applications but unfortunately we can’t catch everything.

First, I want to clarify that the issue I indicated was fixed on June 6th is not the same as anything that you’re reporting here. There was a point in time where the cursor was not changing when at the top edge of the window, preventing any resize attempts entirely. Although the behavior in your video is certainly concerning, you can see that the cursor is appropriately changing when at the top edge of the window.

It’s likely that some of the behavior you’re seeing is due to some combination of screen resolution and taskbar settings that we haven’t accounted for. We’ve had a few other users report their taskbar getting in the way of things (this was after releasing, not before) and, as Ming said, we have an open issue for it that will get looked at. Unfortunately, I can’t say when that will be at this stage.

For reference, the minimum window size is 1024x768 so if your taskbar is set to always display and you’re at a resolution around that size, I could see that as leading to things being covered. Setting the taskbar to auto-hide or unlocking it could be potential workarounds for the time being.

I wanted to include a gif of the resize behavior that I’m seeing on my end; apologizes for the low framerate in advance, I needed to get it down to a size that would upload. This isn’t to discount your issues - you’re clearly running into problems that we want to do our best to address - but to show that we aren’t intentionally ignoring issues that we’re seeing in house, we simply aren’t seeing these issues on our machines.

We can only address problems after we’re made aware of them, unfortunately, so thank you again for bringing them to our attention. It would be very helpful if you could reach out to our support staff at support@trainerroad.com so that we can establish a better communication channel and gather more information from you. In the meantime, we’ll do our best to find the root causes and fix anything on our end that could be a factor. :slight_smile:

As a note, we’d certainly like you to stay on the new application and receive updates but you can download a ā€œlockedā€ version of our old Windows application here if you don’t want to use the new application at this time.

2 Likes

Thanks for the follow up Geoff and for understanding my frustration. I didn’t mean to imply that you were ignoring issues you were experiencing in house, but when it takes a user a matter of seconds to have glaringly obvious issues, I would suggest to you that it’s likely the product wasn’t ready for release. Just my .02

I do suspect you’re correct regarding the resolution as I currently am running TR on a 4k television but scaled to 300% so it could be pushing that 768 vertical size. I’ll experiment with dropping the scaling a bit and see if that makes any difference on the resizing issue.

With regard to the spacing around the taskbar when in minimal mode, since the window is obviously no where near 768 pixels when in minimal mode, I don’t suspect that’s the issue with there. I run TR in minimal mode 100% of the time to allow for Netflix/Zwift/etc to run on top, so that particular issue is probably the most obvious for me.

Thanks again for the follow up and let me know if there’s anything else I can provide that might help expedite a resolution.

1 Like

hi all, my first post!

my mac just had an update to the TR software (10Jul2019 UK), followed by a restart, device rejoin and spin down.

i am working through the sweet spot base mid volume 1, and just did carillion -4. after the second main interval the power did not reduce to 90w for another 12-15 seconds after the effort segment was complete.

after the workout was completed, the calendar updated and then the programme crashed, prompting a force quit.

the programme rebooted fine. i’m on a 2015 macbook pro 13" if thats any help!

Hey there,

Sorry to hear about those issues. I took a look at the ride log for Carillon -4, and it looks like there was a dropout that happened right at the end of that interval, so the Erg command to reduce the resistance didn’t get through until it reconnected. It looks like you had a KICKR SNAP paired via Bluetooth - is that correct? Any other devices paired?

These happen as one-offs sometimes. I don’t really have enough information to say whether or not this is a bug that is specific to the new app. That said, if you keep running into this issue, please keep me in the loop!

As far as the crash goes - what exactly happened? Did the app go blank and you had to force quit and restart? Or did it actually close itself?

Hi Ming, thanks for the reply.

I wasn’t aware my snap was connected through Bluetooth, I use an ANT+ dongle which I usually use to pair the snap and heart rate monitor (unless it’s been using Bluetooth the whole time!). These are the only 2 devices I had connected.

I’m new to TR, but was on zwift previously where a drop out usually creates a zero reading! Worth knowing though in case it happens again, will keep an eye on it.

Yes - the crash made the screen go blank and the load wheel just sat there turning for quite some time. I had to force quit.

Thanks!