In this guide, we will show you the steps to fix the Safari crashing issue on iPhone when searching a specific query. The built-in browser in the Apple ecosystem is enough to checkmark most of the prerequisites that one could have asked for. This when combined with this deep integration into numerous Apple services makes it a clear-cut choice for many users out there. However, in spite of all the goodies that it has to offer, it isn’t free from its fair share of issues either.
@AppleSupport hello, I have a very strange issue with my new iPhone 14 and my mothers new iPhone 14. When we start to type Walmart “Wal” into the search engine the phones instantly close safari. See video below.. please help? pic.twitter.com/P5mq1ahaih
— 805 🇺🇸 (@Dakodes) November 14, 2022
As of now, numerous users have voiced their concern that Safari is crashing on their iPhones when they are searching for a specific query. In most cases, the browser crash as soon as a user inputs the first three letters and is about to enter the fourth one. For example, if you are searching for Walmart, then right after typing the letter ‘l’, the browser would crash.
Apart from that, some users have also reported that Safari crashes when they hit the space key in the search result. So if you are searching for best buy, then as soon you hit Space after best, expect the browser to force close right away. While this is no doubt quite an infuriating issue, but there does exist a nifty workaround that should help you rectify this bug. So without further ado, let’s check it out.
Fix Safari crashing on iPhone when searching a query [Fix]
The culprit behind this issue is the Safari Suggestions feature. So as of now, you should consider disabling it, which could be done using the instructions given below.
- Head over to the Settings menu on your device.
- Then select Safari from the list of apps.
- Finally, disable the toggle next to Safari Suggestions.
That’s it. These were the steps to fix the Safari crashing issue on iPhone when searching a specific query. As far as the official stance on this matter is concerned, the developers are aware of this issue, but they haven’t given out any ETA for the rollout of a fix. As and when that happens, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet. [UPDATE: The issue has now been fixed].
