iOS 13 Public Beta 1 Is Exact Same As iOS 13 Beta 2 Released To Developers
Apple has officially pushed iOS 13 into its public beta release track but, be warned, it comes with a few words of caution. A number of high-profile developers, including Guilherme Rambo, are advising against the installation due to platform instability and the fact that iOS 13 public beta 1 is identical to iOS 13 beta 2 released to developers.
It is certainly not unusual for Apple to involve the general public in its testing. Each year the Cupertino-based business pushes new versions of iOS into the public domain ahead of an official release.
This generally happens after a number of developer-only builds have been released and once Apple is confident that all of the major issues have been resolved. Public testers were expecting this to happen in July of this year and have been psyching themselves up based on that roadmap.
Now, for one reason or another, Apple has decided to accelerate that release and make a version available to public testers. Interestingly, that version is identical to the second beta released to the development community. So, iOS 13 developer beta 2 is equal to iOS 13 public beta 1 in terms of build numbers.
It’s an extremely interesting and bold move by Apple considering that the general consensus is that iOS 13 beta 2 is extremely buggy – perhaps more buggy and unstable than the initial release – and has very specific parts of the platform which are borderline unusable. The aforementioned Guilherme Rambo has highlighted this and is warning the public against installing the build:
Just a reminder that the iOS 13 public beta released today is the same build as iOS 13 developer beta 2, which is supper buggy, especially with AirPods and AirPlay-related things. DO NOT install it.
Rambo is also reminding the public that beta releases are expected to be buggy by their very nature and should not be installed on main devices that a user relies on actually working. This doesn’t just apply to system-level features but also third-party apps that some people rely upon as there is no guarantee that those apps will actually function with iOS 13 until later in the year when the firmware is officially released.
This can be particularly taxing for people who rely on banking applications or apps for work which haven’t been updated to offer compatibility with the changes within iOS 13.
If you are planning on testing out iOS 13, keep the above public service announcement in mind, and, remember, file bugs and feedback with Apple as often as possible.