Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 26 Speculation Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
It's interesting that the previous build was 23A5318c and is now an "f" build at 23A5318f.

It's somewhat apples to oranges, but iOS 18.0 had an "f" build at beta 5 but jumped to a "b" build at beta 6.
 
  • Like
Reactions: NBKindaGirl
Getting "update failed" trying to update my Ulta 2 to 11.6.1 with the revised iOS DP6. Frustrating, but not the end of the world.

Anyone else having this issue?
 
Dwalls90 said:
It's interesting that the previous build was 23A5318c and is now an "f" build at 23A5318f.

It's somewhat apples to oranges, but iOS 18.0 had an "f" build at beta 5 but jumped to a "b" build at beta 6.
Click to expand...
The letter at the end indicates the number of compiles a specific build has gone through.
So build 23A5318 was compiled three times (23A5318a, 23A5318b and 23A5318c, the latter was released as beta 6).
Now the re-release has been recompiled three more times (23A5318d, 23A5318e and the one released, 23A5318f).

The letter starts again at a, if the actual build number changes. So if there‘d be a build 23A5319, the first compile would be 23A5319a. If errors occur, the second compile is 23A5319b, the third one 23A5319c.
If they change the build to 23A5320, it starts at „a“ again.

Summarized: as long as the build number stays the same, a „higher“ letter means newer version/compile of that specific build.
 
  • Like
Reactions: fciscus, mjs916, Blue Hawk and 6 others
Cobold said:
The letter at the end indicates the number of compiles a specific build has gone through.
So build 23A5318 was compiled three times (23A5318a, 23A5318b and 23A5318c, the latter was released as beta 6).
Now the re-release has been recompiled three more times (23A5318d, 23A5318e and the one released, 23A5318f).

The letter starts again at a, if the actual build number changes. So if there‘d be a build 23A5319, the first compile would be 23A5319a. If errors occur, the second compile is 23A5319b, the third one 23A5319c.
If they change the build to 23A5320, it starts at „a“ again.

Summarized: as long as the build number stays the same, a „higher“ letter means newer version/compile of that specific build.
Click to expand...
That’s a great breakdown.

What exactly is “compiling”? Is that essentially running the software through a “check” of sorts until it’s “error free”?
 
s2mike said:
That’s a great breakdown.

What exactly is “compiling”? Is that essentially running the software through a “check” of sorts until it’s “error free”?
Click to expand...
Simple explanation of compiling example. The IOS program that runs or operates the iPhone is generated or starts out with gifted programmers who write the code with instructions. Let say they
s2mike said:
That’s a great breakdown.

What exactly is “compiling”? Is that essentially running the software through a “check” of sorts until it’s “error free”?
Click to expand...
ChatGPT,
iOS compiling is the process of taking your human-readable source code (in languages like Swift or Objective-C) and turning it into machine code that an iPhone, iPad, or other Apple device can run.


Here’s the breakdown in plain terms:


  1. You write code – This is the text you write in Xcode (Apple’s development environment).
  2. Compiler steps in – For iOS, Apple uses compilers like Swiftc (for Swift) or Clang (for Objective-C/C/C++). These:
    • Check for syntax errors
    • Convert your code into an intermediate format
    • Optimize it for speed and size
    • Translate it into binary machine instructions
  3. Linking happens – The compiler connects your code with Apple’s frameworks (UIKit, SwiftUI, etc.) and any libraries you use.
  4. Final product – You get an .app file (or more precisely a signed bundle) that runs on iOS.
  5. Code signing – iOS won’t run unsigned apps, so Xcode signs it with your Apple Developer credentials to make sure it’s trusted.

Think of it like this:


  • Your code = recipe written in English
  • Compiler = chef that translates it into a meal the iPhone can actually “digest”
 
  • Like
  • Haha
Reactions: LutzRFrank, mjs916, Hedkandi and 3 others
Travis299 said:
Simple explanation of compiling example. The IOS program that runs or operates the iPhone is generated or starts out with gifted programmers who write the code with instructions. Let say they

ChatGPT,
iOS compiling is the process of taking your human-readable source code (in languages like Swift or Objective-C) and turning it into machine code that an iPhone, iPad, or other Apple device can run.


Here’s the breakdown in plain terms:


  1. You write code – This is the text you write in Xcode (Apple’s development environment).
  2. Compiler steps in – For iOS, Apple uses compilers like Swiftc (for Swift) or Clang(for Objective-C/C/C++). These:
    • Check for syntax errors
    • Convert your code into an intermediate format
    • Optimize it for speed and size
    • Translate it into binary machine instructions
  3. Linking happens – The compiler connects your code with Apple’s frameworks (UIKit, SwiftUI, etc.) and any libraries you use.
  4. Final product – You get an .app file (or more precisely a signed bundle) that runs on iOS.
  5. Code signing – iOS won’t run unsigned apps, so Xcode signs it with your Apple Developer credentials to make sure it’s trusted.

Think of it like this:


  • Your code = recipe written in English
  • Compiler = chef that translates it into a meal the iPhone can actually “digest”
Click to expand...
Beautiful. Thanks for this!
 
  • Like
Reactions: mjs916 and Travis299
drak22 said:
They've released the public beta and developer beta review for iOS 26, along with new releases for iOS 18 and other stable operating systems. Apple has really hit the update button today haha
Click to expand...
From my sources within Apple:

“Apple technicians got the Beta Release button so immaculately clean that Tim Cook was very impressed, and enjoyed clicking it repeatedly so many times that all of the betas began to roll out in an unprecedented fashion. Apple technicians seem to have engineered the absolute perfect cleaning solution for the beta release button, and there’s word that some engineers even modified the button to include fun haptics like those found in the Apple Pencil Pro! It seems like they have arrived at the perfect design formula to entice Tim Cook to want to click the button.”
 
Cobold said:
The letter at the end indicates the number of compiles a specific build has gone through.
So build 23A5318 was compiled three times (23A5318a, 23A5318b and 23A5318c, the latter was released as beta 6).
Now the re-release has been recompiled three more times (23A5318d, 23A5318e and the one released, 23A5318f).

The letter starts again at a, if the actual build number changes. So if there‘d be a build 23A5319, the first compile would be 23A5319a. If errors occur, the second compile is 23A5319b, the third one 23A5319c.
If they change the build to 23A5320, it starts at „a“ again.

Summarized: as long as the build number stays the same, a „higher“ letter means newer version/compile of that specific build.
Click to expand...
Thanks - I didn't actually know this. If both of these betas took 3 tries to compile (a-c, d-f), it's safe to say they took the same compilation attempts, so are the same?
 
mcvaughan said:
I predict so.
Click to expand...
I’m also going to check on my watchOS 26 beta testers to see if they have the updated iOS build on their iPhones. I want to know if the update allows them to perform SPO2 readings from their US region Series 9/10 and ultra 2 Apple Watch models. As far as I know, there’s no mention of the SPO2 app’s comeback or alternative approach on rerelease ios 26 beta 6, or any indication of changes similar to our public release of iOS 18.6.1 and watchOS 11.6.1. However, it’s best to check it out for yourself as well.
 
Dwalls90 said:
Thanks - I didn't actually know this. If both of these betas took 3 tries to compile (a-c, d-f), it's safe to say they took the same compilation attempts, so are the same?
Click to expand...
I think people are putting too much (incorrect) weight on an earlier letter build like an 'a" build, as being 'better'.. If it passes through QA and then they find an issue, recompile, find another issue, recompile again, maybe again and again? Doesn't that also imply that some last minute issues may have been addressed and now that later letter build or a 'j' build, might actually run smoother than a 'b' build.
 
  • Like
Reactions: Travis299, Cobalt Blizzard, NBKindaGirl and 5 others
For you us guys and the blood oxygen thing:

either it will be available on Monday with db7 or what I believe more is that it will be available with official release in september, but we will see in 2 days
 
  • Like
Reactions: NBKindaGirl
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back