Cookies are the essential part of every browser and, without them, some sites won’t function as intended. On the other hand, without cookies, the sites you’re visiting are unable to track you and therefore, your sensitive data is protected or even interfere with the other sites. Essentially, you need to clear the cookies from time to time. However, that seems to be a problem with certain iPhone 6 users.
Namely, some of the users reported issues with the Safari browser closely related to cookies, especially after 10.3. iOS update. To be more precise, some of them were not able to delete the certain cookies. It seems that the particular cookies are persistent to remain within the Safari browser and they somehow override the deletion standing firm on 0 KB of space.
The ones with the latest version can only wait for next update to address this issue, while others can try out some of the presented workarounds. Hopefully, you can use them to clean all cookies from the app and continue with browsing.
Delete cookies from Advanced tab
Even though there’s a probability that the cookies from some sites won’t get cleaned, there’s a chance that those will be google.com or weather.com which aren’t exactly dangerous. Hopefully, you’ll get rid of some cookies if not all of them. Follow this procedure to clear the browsing data.
- Close Safari completely.
- Open Settings.
- Tap Safari.
- Tap Clear History and Website Data.
- Now, get back to Safari and open Advanced.
- Tap Website Data.
- Select Remove All Website Data.
Additionally, you can select the Edit within the Website Data, and clear the relentless cookies individually.
Update Safari app
Furthermore, you should try and update the Safari app. We can’t be sure is it a bug or a temporary issue, but the latest version may as well resolve your problem instantly. If your auto-update feature isn’t enabled, you can look up for the update manually on the Apple Store in a few easy steps.
- Open Apple Store app on your iPhone 6.
- Tap Updates.
- Tap on Safari if available to update it.
- Close the App and try deleting the cookies.
If the problem is persistent, move on to the next steps.
Force restart your iPhone
If the problem is more of an overall issue rather than just the native browser bug, you can try and force restart your iPhone 6 to clear all the conflicts between the app and system. That’s easy to do by following these steps:
- Press and hold the Home Button.
- While holding the Home Button, press and hold the Sleep button.
- Hold for the approximately 15 seconds and the device should restart.
- The Apple logo should appear.
- Now, navigate to the Settings > Safari > Advanced > Website Data.
- Tap Remove All Website Data.
If those pesky cookies are still there, you should move to the next solution on the list.
For the time being, this problem mostly occurs with users that updated to iOS 10.3. Without a doubt, this specific version has some issues and we hope that some of the next versions will resolve this issue. We can expect the next patch (10.3.2) in the upcoming weeks since it’s still in the Beta phase. But, since we aren’t aware of the exact release date, you can from time to time check for the updates. To do so, follow the instructions:
- Tap Settings.
- Open General.
- Tap Software Update.
- If there’s an upgrade available, tap Download & Install.
Reset All Settings
Additionally, you may try and reset all settings. Have in mind that this will delete your current setup, preferences and network settings, so make sure to back it up timely before you perform the reset.
Follow these steps to perform the reset of all settings:
- Tap Settings.
- Open General.
- Tap Reset.
- Tap Reset All Settings.
- Enter your passcode and Apple ID.
- The phone will restart and you’re good to go.
However, if even this measure was of little or no avail, you may as well perform the factory reset. We’re aware that this is the last resort but sometimes is hard to overcome issues without the clean start.
That should do it. We certainly hope that these workarounds point you in the right direction. Additionally, don’t forget to share your experience or an alternative workaround in the comments below.