I think one thing you are missing is that there are probably hundreds of builds that never leave the Apple campus due to instability, etc... And for at least the first 4 or 5 betas that are released, the public beta lags by at least a day (and in the case of the first 2 no public beta was released at all). And last week, when there was a problem, Apple also did not release a public beta until it fixed the developer beta. The background bugginess that is still present is simply an occupational hazard of using these releases.I'm surprised this made it to the public BETA release cycle. As it didn't arrive last week I figured it was deemed too buggy and unstable to release the public BETA channel. But obviously it was only due to Apple not having enough time to re-compile in order to get it working for the iPhone 7 and 7 Plus, hench why we got the g-compile this week which also released as public BETA.
One have to wonder what the point of having developer and public BETA's are at this point in time. I always looked at it like Microsoft's Insider Preview Fast Ring and Slow Rings. Fast Ring is meant for developers, you get delivered early builds very often so you have extra time to test and optimise your apps but you are aware that very little care goes into the builds so be aware. And Slow Ring are for eager consumers who want to test out new releases before they are publicly available, but these builds are less prone to have dealbreaking bugs as they are only pushed when a build from the Fast Ring has been deemed stable enough to reach the next ring.
Obviously Apple's BETA's are not like this because about every build no matter how buggy they are in the developer BETA still gets pushed as a public BETA.
That is a very relevant question. Hopefully next week but this weeks update could mean the week after.Should we still expect beta 4 next week? Or has the release been shifted by an additional week due to the revised beta 3 this week?
I'm surprised this made it to the public BETA release cycle. As it didn't arrive last week I figured it was deemed too buggy and unstable to release the public BETA channel. But obviously it was only due to Apple not having enough time to re-compile in order to get it working for the iPhone 7 and 7 Plus, hench why we got the g-compile this week which also released as public BETA.
One have to wonder what the point of having developer and public BETA's are at this point in time. I always looked at it like Microsoft's Insider Preview Fast Ring and Slow Rings. Fast Ring is meant for developers, you get delivered early builds very often so you have extra time to test and optimise your apps but you are aware that very little care goes into the builds so be aware. And Slow Ring are for eager consumers who want to test out new releases before they are publicly available, but these builds are less prone to have dealbreaking bugs as they are only pushed when a build from the Fast Ring has been deemed stable enough to reach the next ring.
Obviously Apple's BETA's are not like this because about every build no matter how buggy they are in the developer BETA still gets pushed as a public BETA.
I see this absolutely this way. Don’t understand why Apple sees these kinds of betas as public?!
Any fixes for all calls going to voicemail? Pb2 iPhone XR. And yeah it’s been reported..... Don’t want to downgrade.
No it’s not on. I’ve turned off 4g to see if this helps.Have you got the option for forwarding witheld numbers to voicemail on (Silence Unknown Callers)? I saw some people saying this had randomly turned on in DB2.
I agree with Monday the 15th only if 12.4 drops this Friday .. If not I think 12.4 will release on Monday the 15th and then new beta on Tuesday the 16th for iOS 13 ... just my guess
Wonder if the credit card will drop next week too
I have a feeling it will drop alongside 12.4 on Monday
Wonder if the credit card will drop next week too
I wonder when Apple are going to start letting us testers loose with the changing of fonts???
I think fonts are to be used within apps so they won't be available until the API is live in September. Unless Apple can make them available in their own stock apps beforehand, maybe someone who knows more can chime in on that.
No, I think he means that the fonts are apps and since they rely on iOS 13 and Apple won't approve any iOS 13-specific third party apps until shortly before iOS 13 goes live, there won't be any available until then. You might search to see if any developers are running betas of font apps and you might be able to try out via TestFlight.So they wont be able to be used system wide?
No, I think he means that the fonts are apps and since they rely on iOS 13 and Apple won't approve any iOS 13-specific third party apps until shortly before iOS 13 goes live, there won't be any available until then. You might search to see if any developers are running betas of font apps and you might be able to try out via TestFlight.
I thought in the iOS 13 keynote it was said that we would be able to download fonts via the app store.
You won't have the ability to apply the fonts system-wide... you will be able to apply the fonts to various apps (so the font will only change within the app you choose and not across iOS) as long as the developer has updated their app for it. And that last part is why it's not available for testing yet.
I understood it as fonts will be downloadable to be used by apps such as Word etc. in documents when actually ”writing” text. Not to change the actual font that the system or apps uses.No, I think he means that the fonts are apps and since they rely on iOS 13 and Apple won't approve any iOS 13-specific third party apps until shortly before iOS 13 goes live, there won't be any available until then. You might search to see if any developers are running betas of font apps and you might be able to try out via TestFlight.