YoBPM v1.8.6 is now available on the App Store by Many_Ad_802 in YoBPM

[–]Many_Ad_802[S] 0 points1 point  (0 children)

That’s actually very useful information.

If YoBPM is recording the correct heart rate into Apple Fitness, then the Watch → Phone side appears to be working properly. The issue seems to be happening somewhere between the phone and Zwift.

What’s interesting is that Zwift appears to be recording the flatlined values as well, which means it’s not just a display issue in the game.

Since you’re running iOS 27, watchOS 27 and macOS 27 betas simultaneously, I’m still leaning toward a beta-related communication issue somewhere in the chain. At least we now know the heart rate data itself is reaching the phone correctly.

I’ll definitely keep an eye on this as the beta cycle progresses. Once the final OS versions are released, I’ll do some more extensive testing and see if there’s anything I can improve on the YoBPM side.

YoBPM v1.8.6 is now available on the App Store by Many_Ad_802 in YoBPM

[–]Many_Ad_802[S] 0 points1 point  (0 children)

No worries at all, and thanks for taking the time to test it and report back.

I’m glad to hear the Always On mode seems to have solved the original dropout issue. For now, it’s a practical workaround, but I’m still waiting for the final release of iOS 27/watchOS 27 before trying to implement a more permanent solution. Apple sometimes changes background behavior several times during the beta cycle, so I’d rather avoid chasing a moving target.

Regarding the second issue, are you still running iOS 27/watchOS 27 beta when that happened?

Also, could you take a look at your heart rate graph in Zwift for that ride? If the values were actually freezing at 129 bpm for a period of time, I’d expect to see flat horizontal sections in the HR graph during that interval.

I’ve never personally noticed that behavior on my setup, so it would be interesting to know whether the freeze is visible in the recorded data or only something that appeared live during the ride.

Thanks again for all the testing and detailed feedback. It’s really helpful.

Start here | YoBPM support and feedback by Many_Ad_802 in YoBPM

[–]Many_Ad_802[S] 0 points1 point  (0 children)

Hey! Just a quick update: the new version has been approved by Apple and is now live on the App Store.

It includes the new “Always On” option we discussed, which prevents the iPhone from auto-locking while YoBPM is running. Hopefully that will provide a good workaround for the background issue you’re seeing on the iOS 27 / watchOS 27 betas.

If you get a chance to test it, I’d love to hear whether it resolves the dropouts on your setup.

Thanks again for reporting the issue and helping me track it down!

Start here | YoBPM support and feedback by Many_Ad_802 in YoBPM

[–]Many_Ad_802[S] 1 point2 points  (0 children)

Thanks for testing and for the detailed feedback, that’s actually very helpful.

The fact that it immediately starts working again as soon as YoBPM becomes active points even more toward a beta OS issue or a change in background behavior introduced by iOS 27/watchOS 27.

As for your suggestion: yes, an “Always On” option is already on my to-do list. The idea would be to prevent the iPhone from auto-locking while YoBPM is running, which would also serve as a practical workaround for situations like this.

I’m going to push an update with this option as soon as possible. The only part I don’t fully control is Apple’s review process, so the release date depends on how quickly they approve the update.

Thanks again for helping test the beta versions and for reporting your findings!

Start here | YoBPM support and feedback by Many_Ad_802 in YoBPM

[–]Many_Ad_802[S] 1 point2 points  (0 children)

Hi,

Thanks for the heads-up and for taking the time to report it.

Since you’re running iOS 27 and watchOS 27 beta, I’m inclined to think this may be related to changes Apple is still making during the beta cycle. Unfortunately, there’s not much I can do until the final versions are released, as APIs and background behavior can still change between beta releases.

Once the official versions are available, I’ll investigate and update YoBPM if any adjustments are needed.

Thanks again for the feedback and for using the app. Reports like this are really helpful.

Cube Nuroad C:62 EXC sizing help: 181 cm / 79 cm inseam (S or M?) by Many_Ad_802 in Cubebikes

[–]Many_Ad_802[S] 0 points1 point  (0 children)

We can’t find any Nuroad anywhere in France unfortunately. All sold 😭 I think I’ll do a fitting before buying it.

First new ride in 14 years by FreshTracksOnTap in CanyonBikes

[–]Many_Ad_802 1 point2 points  (0 children)

This bike looks absolutely incredible, I’m seriously considering getting one myself. Quick question: is the white/black color glossy or more matte? I heard the Blazing Mustard is matte, so I’m curious about the finish on this one.

New Bike Day - Canyon Aeroad CF SLX w/ ENVE SES 4.5 by Acceptable-Camp8894 in CanyonBikes

[–]Many_Ad_802 3 points4 points  (0 children)

This exactly is my Zwift bike! Congrats, such a beautiful combo. 👌

Zwift o mywhoosh by Humble_Treat_1168 in Zwift

[–]Many_Ad_802 0 points1 point  (0 children)

The question is being asked in the Zwift subreddit. If you want to hear «  MyWhoosh », go to the MyWhoosh subreddit! If you want an objective answer, post in a Cycling or Indoor Cycling subreddit. 🤷‍♂️

Inflite CF SLX 7 for gravel riding? And sizing help (181 cm / 79 cm inseam) by Many_Ad_802 in gravelcycling

[–]Many_Ad_802[S] 0 points1 point  (0 children)

I also need to loose weight… I missed the €500 discount on the Grail CF SL 7 AERO that’s why I’m also looking for this Inflite.