Since upgrading to iOS27 yesterday...
Can't open Apple Podcasts and icon has disappeared from my UI (can search for it, but nothing happens when I press open)
Can't open Safari - same deal.
I am on iPhone mini 13 iOS version 27.0.1
Since upgrading to iOS27 yesterday...
Can't open Apple Podcasts and icon has disappeared from my UI (can search for it, but nothing happens when I press open)
Can't open Safari - same deal.
I am on iPhone mini 13 iOS version 27.0.1
Posted on Oct 3, 2026 3:04 PM
Oct 4, 2026 1:57 AM in response to cordelia176
You may try some of these steps. Please check after each step...
If none of the above steps resolve the issue, it is recommended to reach out to Apple Support or visit an authorized service center for further assistance. They can provide specific guidance based on your device model and iOS version.
Oct 4, 2026 1:58 AM in response to cordelia176
Also check if you have accidentally selected this--> Settings > Screen Time > App Limits > Add Limit > [Search Field] Type Safari > Select Safari
See the pic below
Oct 4, 2026 1:56 AM in response to cordelia176
cordelia176 wrote:
Since upgrading to iOS27 yesterday...
Not every issue an individual encounters on their device can be attributed to an iOS update. iOS 27 or later may have coincided with what you are experiencing, but that does not mean the issue was triggered by iOS. Coincidence in timing is not, by itself, evidence of causation.
If the update itself were the root cause, then every device running that same version of iOS would exhibit the identical problem. In such a scenario, the forums would be flooded with countless posts reporting the same malfunction, creating an unmistakable wave of complaints that no one could possibly overlook.
The absence of such widespread reports strongly indicates that the issue is not a general, system-wide problem with iOS 27 or later, but rather something specific to the individual device, its configuration, installed apps, settings, hardware, or another interacting factor.
In short: iOS 27 or later may be a coincidence in timing, but there is no basis to conclude that iOS itself triggered the problem simply because the issue appeared after the update.
Originally posted at discussions.apple.com/thread/256369840