Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Wow, back to a ‘d’ build. Would have been expecting an ‘a’ or GM at this stage given how long this cycle has gone.
RC or public releases, in most cases, comes after an 'a' build. The next build could very well be an 'a' build but I don't think it will be RC or public.
I'm referring to the not downloaded tracks. No different than jumping to a time slot in an HD YouTube video as opposed to a 720 or 480 video.
No, not convinced. I believe the letter indicates how many times Apple had to tweak the process on a particular day to get a viable ipsw. So the next day they could run the tweaked process and get an A build. Hence the build letter is meaningless
Yes. I also think that these build letters are only the number of iterations needed to obtain a « viable ipsw file » to be released to testers, and doesn’t presume how far/near is the next public build.
Franck
No chance, since it’s a d build, there’ll definitely be a RC build before final release. 🤔
No it isn't exactly. Typically near an end of a version there are less changes to code therefore less commits so they can release several 'a' builds back to back before a final. Folks equate this to "almost ready to release". But Apple could just as easily release 15 betas all 'a' builds during the entire beta cycle before a release.
Exactly this.
Exactly, Has no bearing on anything other than how many commits a particular build had before releasing it. Look back at iOS 14.5 betas. Betas 4,5,6,7,and 8 were all 'a' builds.
Last edited:
No chance? Look at iOS 14.4. Beta 2 was 18D5043d then the very next build was the release version 18D52. There never was an 'a' build for iOS 14.4. There may or may not be an RC actually released to devs 1st but not necessarily since an RC is the release version.
That's a good explanation. For my understanding, what is this process or iterations that Apple has to tweak to obtain a viable .ipsw?
Apple software engineers must be continuously testing successive iterations, so they should be having the .ipsw corresponding to each iteration for them to deploy and test internally. So when Apple decides to go with a particular build they should be having corresponding .ipsw ready. So what is it that Apple has to tweak to obtain a viable .ipsw? When you have a build ready then is it not a one step process to obtain the .ipsw from the build by compiling the code?
So why does the last letter vary?
Apple software engineers must be continuously testing successive iterations, so they should be having the .ipsw corresponding to each iteration for them to deploy and test internally. So when Apple decides to go with a particular build they should be having corresponding .ipsw ready. So what is it that Apple has to tweak to obtain a viable .ipsw? When you have a build ready then is it not a one step process to obtain the .ipsw from the build by compiling the code?
So why does the last letter vary?
Why no chance? I’ve given precedent. iOS 13.7, which came out between WWDC and iOS 14’s release, had no RC, it went from beta straight to public release. Apple have done it many times before where they went straight to public release, which is due to the release not being deemed to need it, as minor fixes that don’t require an RC. iOS 14.7 falls into that critErica.
iOS 14.7 and iOS 15 betas have no fix. It’s hardware issue, but the user is in denial, and being lazy in regards to getting it replaced, which many other owners have done already, as per the threads I’ve read on the Apple community pages.
Yeah, if I was having a hardware issue, I would have had Apple look into replacing my hardware. Maybe even setting it up again in store, to confirm whether or not the hardware is still having an issue.
I think the user is waiting until just before Applecare expires and getting a swap out to a “new” phone.
Ahhhh, that's a great idea. Then I'd assume there'd be no need to keep posting about it then, right? Right?? 🙃🤣😇
Wouldn’t AppleCare just swap it for another of the same model?
Yes, but there's been times in the past where there was a small number in a batch that were bad or something similar. Getting a phone 3-4 months later, you're pretty much guaranteed to get a different batch....
...which means if I had that issue still, I would have had it replaced 🤣
Yes it will be a phone of the same specification. By ‘new’ I meant one with no scratches or dings and with a brand new battery. Interestingly it won’t be the “same model” because Apple use different model numbers for new phones and the swapped out phone equivalents.
Anyhow we ought to get this thread back on topic.
It Hans't even proven it's a hardware issue, I'll wait a little longer, some people have been getting a new device or installing new software and having green tint show up.
In the end we are all guessing if it's hardware or software. 😅
If it was software, it would be more common. Instead it’s a handful in comparison to the amount of devices out there.