Following an exceptionally-long and unheard-of grace period, Apple has officially stopped signing both iOS 12.1.1 and 12.1.2 Tuesday evening, a move that packs some serious implications for the jailbreak community.
Update: iOS 12.1.1 beta 3 is apparently still being signed at the time of this writing. Downgrade immediately while you have the chance!
Apple first launched these firmware versions on December 5th and December 17th respectively, each to address small bug fixes and performance improvements in the operating system. But as we know, no software is entirely bug-proof.
Not long after tihmstar published his iOS 11.4-11.4.1-centric tfp0 exploit for headphone jack-enabled handsets, security researcher Brandon Azad followed up by releasing an exploit of his own intended for devices running iOS 12.1.2 and earlier.
Azad shared the news via Twitter Tuesday afternoon, including a link to documentation encompassing the exploit:
Are you finding it impossible to restore your iPad from an iCloud backup?
Apple on Thursday released an updated version of the iOS 12.1.2 software with a new build number 16C104. The iPhone-only software update has arrived just three days following the initial release of iOS 12.1.2 with its original build number 16C101.
Apple's acknowledged that the iPhone-exclusive iOS 12.1.2 software update has indeed circumvented a pair of Qualcomm patents—in spite of Qualcomm's claims to the contrary.
Apple today released iOS 12.1.2, a minor software update for iPhone and cellular iPads that contains bug fixes for the eSIM feature, arriving two weeks after the release of iOS 12.1.1.
Apple on Tuesday issued new betas for those in the public testing program. The same first betas of iOS 12.1.2, tvOS 12.1.2 and macOS 10.14.3 that were released to developers yesterday, can now be installed by public testers using their respective OTA mechanisms.
Apple on Monday issued new betas for iOS 12.1.2, watchOS 5.1.3, tvOS 12.1.2 and macOS 10.14.3 to developers. Those with Apple developer accounts can install the new betas either directly from the Dev Center or via their respective over-the-air mechanisms once the proper configuration profile has been installed.