Apple has launched iOS 15.3 and iPadOS 15.3 that brings a repair for a important bug that affected Safari in addition to different browsers. The just lately introduced replace is the third main replace for iOS 15 that launched final 12 months in September. The Safari browser bug has additionally affected customers on macOS. The bug affected the browser historical past on Apple units operating the aforementioned working programs. Separately, Apple is reportedly rolling out a repair for the syncing points in iCloud that impacted third-party purposes.

As per a blog post, Apple is rolling out iOS 15.3 and iPadOS 15.3 updates for eligible iPhone and iPad fashions. The replace brings a repair for the important bug that affected Safari in addition to different browsers the place the searching historical past was susceptible to being leaked. The bug was found earlier this month and affected customers on iOS, iPadOS, and macOS. With this bug, attackers can acquire entry to customers’ current searching historical past and even establish the linked Google account.

Users of macOS might keep away from this case by switching to a third-party browser however this was not the case for iOS and iPadOS customers. With the update for macOS in addition to iOS and iPadOS, the vulnerability can now not be used to steal searching historical past together with identification particulars of Safari customers. The replace ought to attain all customers routinely over-the-air, nonetheless, eager customers can test for the replace by heading to Settings > General > Software Update.

Separately, a report by 9to5Mac states that Apple is rolling out a repair for iCloud for its sync and CloudKit points that has been affecting third-party purposes. Some builders have mentioned that Apple has fastened the problem however didn’t element what the underlying situation was or what triggered it. However, Apple did acknowledge the problem led to customers receiving a “Service unavailable” message with an Error 503 code.

The Cupertino-based big acknowledged that the error normally occurred when request-throttling is activated for a selected person, however a bug was impacting the safeguard that led to a excessive variety of errors. Apple is reportedly nonetheless reaching out to third-party app builders, hinting that the repair for the bug should still be rolling out. Apple is but to publicly acknowledge the bug that affected the third-party apps.