Replies: 2 comments
-
Is there any public place that would help me understand what commit the actual build number cross-references? (In case I'd like to see the underlying changesets to test and verify their effect.) |
Beta Was this translation helpful? Give feedback.
-
Turns out I was not subscribed to the current beta testers link, might have been stuck on some older group id that provided only a few builds — now with the correct invite I can see many more builds and get all the betas to test: Success. ✅ 🏁 In case someone's looking for the current TestFlight group (or they never got the confirmation mail from the form submission), it's this: https://testflight.apple.com/join/JdsubPZs |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm just curious if there's a place to watch for new beta releases, as GitHub lists only stable channel versions, and I'm having hard time forcing TestFlight into updating beyond the first build it offers.
Or is it to be expected there's always only one single build released on the beta track for every major branch, as TestFlight would suggest: ?
Meaning build 50486 from Feb 3rd was the only v136.x beta built and pushed to TestFlight?
I wanted to confirm a fix that appeared somewhere between 50486 and 50944 few weeks later so I was watching what TestFlight offered, but was stuck on the first and only build it got for that major branch.
(Now with v136.0 release out, the beta app is therefore even behind the release channel, unless the first v137 beta is built.)
Is this normal and always only vX.0b1 is released to TestFlight, or I am missing something important to be able to consume more current beta builds during each train cycle? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions