TR app is not loading after the last MAC OS update

Hello friends,

Last week apple updated its OS Tahoe - 26.3.1.
TR app doesn’t open after the update - after launching it requests your credentials but an error note appears. I have an iMAC and a MacBook Pro and both suffer from this issue. The app is loading on IOS which has been updated at the same time.

Does anyone know how to fix it?

Thanks,
Uzi

No issue on my Mac with the update. Maybe try deleting the app, restart Mac then reinstalling.

This :up_arrow:

I had no issues yesterday after the update.

Thanks. I have done it twice on both computers, but it didn’t work :man_shrugging:t2:

I would contact TR customer support . If the app loads but won’t login, it could be something on the back end.

Support will definitely help you out!

If you don’t mind, follow up here with what you find!

Hi friends,

The following are the instructions from the support team. I followed the additional steps suggested. The app now is launching well.

With newer macOS versions (like Tahoe 26.3.1), apps will only appear in System Settings → Privacy & Security → Local Network after they request local network access for the first time. Because of that, the TrainerRoad app may not show up in the list until it tries to discover devices on your network.

Could you try the following steps?

  1. Open the TrainerRoad app on your Mac.
  2. Go to the Devices tab.
  3. Turn on your trainer, power meter, or other sensors so the app attempts to discover them over the network.

At that point, macOS should prompt you to allow TrainerRoad to access the Local Network. If the prompt appears, please click Allow, and the app should then show up in the Local Network permissions list.

If the prompt doesn’t appear, try these additional steps:

  1. Quit the TrainerRoad app.
  2. Open System Settings → Privacy & Security → Local Network and see if TrainerRoad appears after relaunching the app.
  3. If it still doesn’t appear, restarting the Mac once more and opening TrainerRoad before any other apps can sometimes trigger the permission request.

Since the iPhone app is working normally, this is most likely just macOS not prompting for the permission yet.

1 Like

Thanks for sharing @UI1! :raising_hands: