Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,533
39,373


Apple in iOS and iPadOS 14 allows users to set third-party apps as alternatives to the default mail and browser apps on iPhone and iPad, but a widespread bug appears to revert these settings to Apple's default apps whenever the user's device is rebooted.

ios14-and-default-outlook-feature-1.jpg

The issue was discovered by several users who reported it on social media, and Apple has since confirmed the bug's existence in a statement given to CNET.

"We are aware of an issue that can impact default email and browser settings in iOS 14 and iPadOS 14. A fix will be available to users in a software update," Apple said in a statement.
Until Apple resolves the issue, suffice to say if you've set a preferred third-party browser or mail app over Safari or Apple Mail, you should probably avoid shutting down or restarting your iPhone or iPad, otherwise you'll have to re-select your preferences again each time you boot up your device. Of course, that's unavoidable if your device runs out of battery.

Currently, Chrome, Edge, DuckDuckGo, and Firefox can be set as default browsers, while Spark and Microsoft Outlook can be set as default Mail apps. Users who don't get on with Safari or Apple's native Mail app can choose an alternative and it will be opened automatically whenever the system requires it. As long as they haven't restarted their device, that is.

Article Link: iOS 14 and iPadOS 14 Bug Resets Default Apps to Safari and Mail After Every Reboot
 
Thankfully Web browsing, and email aren't big things I use my phone and iPad for. I prefer a computer for such things. With that said, on the iPad I use the Gmail app, since it's my primary email, and just never bothered to configure apple mail, other than iCloud which is done automatically during setup.
 
bet that's a pain in the butt. People will have no choice when their battery runs out. lol
 
Last edited:
Before this article when I heard about it, it was obviously a bug but nevertheless it's kinda funny that this happened.

I'm surprised this bug wasn't caught in the internal beta, though.
 
This does not bode well for iOS 14. A very basic bug, very easy to find, not caused by some weird, uncommon device usage. And they didn’t catch it before release?

To be fair, the public beta testers are also useless. It’s filled with users who just want to “have the latest” and not actually report anything.

I personally reported 8 bugs. And 7 of them still have the status of “open”. And only 1 of the bugs reports as have 10 similar cases.
 
To be fair, the public beta testers are also useless. It’s filled with users who just want to “have the latest” and not actually report anything.

I personally reported 8 bugs. And 7 of them still have the status of “open”. And only 1 of the bugs reports as have 10 similar cases.

I agree. The bugs you reported are probably low on the list. They'll address them. I stopped doing the betas and only try a major release for a day or two. You are right. I do it to see the latest and greatest. That's pretty much it at this point. I just don't have the time I used to or the patience, honestly. When I did evaluate betas, I submitted every bug I found. That's the whole point, right?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.