Apple Intelligence now features Image Playground, Genmoji, Writing Tools enhancements, seamless support for ChatGPT, and visual intelligence.

Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >

You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

IOS/iPadOS 13.5.1 New Bug

This is partly peculiar to my network setup, but may affect others with a similar setup.


Things were fine until I updated to 13.5.1. Three devices (2 phones (iPhone 8, iPhone SE 2), 1 iPad Pro, different iTunes accounts) are experiencing the same issue. Also tested an iPhone 7 with another account - same issue.


While on Wifi, downloading large apps (over 500MB) results in a popup asking if I'm sure I want to download over cellular, or wait until I'm on WiFi. Also, resetting and restoring the phones and iPad results in all restored apps not actually updating until each is tapped on once pausing then tapping once more to resume - and the large ones giving the cellular message.


Note that the iPad Pro is a WiFi only model. All three devices are on WiFi, and the issue persists even when in Airplane Mode with WiFi on, and cellular data specifically turned off.


The Wifi setup: A cable modem (Rogers) with its Wifi disabled, and another router plugged in, in bridge mode, offering the Wifi. The Wifi runs very well.


If I tell the popup to download anyway, it does, using the Wifi. The devices *think* I'm on cellular. This is not a major issue until you try to download an update or restore. Trying to install the iPadOS 14 beta failed because it doesn't see me as being on a valid Wifi.


Here's the interesting thing: if I activate the cable-modem's Wifi and connect to that instead, the issue does not happen. It's as if IOS is seeing the extra address in between as making the setup somehow as cellular. BTW - it's all one subnet.


Every possible troubleshooting step has been done - including resetting, restoring, etc. I have even tried another router (one is Apple AirPort Extreme, and the other is a DLink).


As mentioned, this started with the 13.5.1 update. Prior to this everything was fine. Also, I have an older iPad on 12.4.7 which is NOT having this issue, and many other devices are also working fine. It is only the 13.5.1 devices affected.


I will report the bug, but wanted to post and see if anyone has a fix, or even if it is affecting anyone else.

iPad Pro 11-inch Wi-Fi

Posted on Jun 26, 2020 1:08 PM

Reply
Question marked as Top-ranking reply

Posted on Jun 28, 2020 11:34 AM

Well, I have tracked down the issue. It's a bit complicated, but now resolved.


It's something with my router (a DLink) that only showed up with the 13.5.1 update.


Why I didn't figure this out when I tested it on just my cable-modem, was that the iPhones seem to be caching and sharing network information. When the iPad was on the dLink, then I eliminated the DLink, and tested my cable-modem, I was then alone on it. To test putting all my devices back, I renamed the cable-modem's wifi to be the same as the DLink's.


The issue cropped up again after a few minutes. It seems the "bug" with IOS 13.5.1 and the DLink makes some cached setting in the iPad, that carries the bug to the cable-modem. Resetting (forgetting the Wifi SSID) had fixed it (so all was good for a few minutes) until more devices came online. They seem to "share" information about their stored SSID settings, including whatever this cached bug was.


Same issue when replacing the DLink with the Apple Extreme router.


Deleting the Wifi SSID off all Apple devices and reconnecting each one resolved the issue on the cable-modem.


Putting the DLink back brought the issue back, proving it was the DLink that had the 13.5.1 incompatibility - and was somehow "infecting" the 13.5.1 devices with some setting.


Removing the DLink, putting in place the Apple router, deleting all the SSIDs from the Apple devices has now removed the issue.


So in summary, the DLink router, which was fine until 13.5.1 is doing something to mess with 13.5.1 devices that they remember, and carry to any other router with the same SSID. Apple has changed something - I'm not qualified to say if it's wrong, but it certainly caused this issue with a DLink router that was fine until the update.


The DLink is no longer part of my network. Perhaps Apple will still resolve this (or DLink will, as it's fairly new and v.1.0 of its firmware is still the latest), but until then, I will live with my old 802.11n, and give up my ultra high-speeds.


This has been an exercise and a half, but it is solved, and may help someone. You may not see the prompt about cellular if you're not downloading something large from the App Store, but you could still hit the issue where it won't download a major IOS update, and doesn't say why, or maybe your Photo Stream isn't working. I do see a lot of people on the IOS 13.6 and 14.0 beta forums complaining that they are stuck while trying to update. I'll ask some of them if they happen to have a DLink router.


Similar questions

9 replies
Question marked as Top-ranking reply

Jun 28, 2020 11:34 AM in response to AndreTheGeek

Well, I have tracked down the issue. It's a bit complicated, but now resolved.


It's something with my router (a DLink) that only showed up with the 13.5.1 update.


Why I didn't figure this out when I tested it on just my cable-modem, was that the iPhones seem to be caching and sharing network information. When the iPad was on the dLink, then I eliminated the DLink, and tested my cable-modem, I was then alone on it. To test putting all my devices back, I renamed the cable-modem's wifi to be the same as the DLink's.


The issue cropped up again after a few minutes. It seems the "bug" with IOS 13.5.1 and the DLink makes some cached setting in the iPad, that carries the bug to the cable-modem. Resetting (forgetting the Wifi SSID) had fixed it (so all was good for a few minutes) until more devices came online. They seem to "share" information about their stored SSID settings, including whatever this cached bug was.


Same issue when replacing the DLink with the Apple Extreme router.


Deleting the Wifi SSID off all Apple devices and reconnecting each one resolved the issue on the cable-modem.


Putting the DLink back brought the issue back, proving it was the DLink that had the 13.5.1 incompatibility - and was somehow "infecting" the 13.5.1 devices with some setting.


Removing the DLink, putting in place the Apple router, deleting all the SSIDs from the Apple devices has now removed the issue.


So in summary, the DLink router, which was fine until 13.5.1 is doing something to mess with 13.5.1 devices that they remember, and carry to any other router with the same SSID. Apple has changed something - I'm not qualified to say if it's wrong, but it certainly caused this issue with a DLink router that was fine until the update.


The DLink is no longer part of my network. Perhaps Apple will still resolve this (or DLink will, as it's fairly new and v.1.0 of its firmware is still the latest), but until then, I will live with my old 802.11n, and give up my ultra high-speeds.


This has been an exercise and a half, but it is solved, and may help someone. You may not see the prompt about cellular if you're not downloading something large from the App Store, but you could still hit the issue where it won't download a major IOS update, and doesn't say why, or maybe your Photo Stream isn't working. I do see a lot of people on the IOS 13.6 and 14.0 beta forums complaining that they are stuck while trying to update. I'll ask some of them if they happen to have a DLink router.


Jun 27, 2020 4:26 PM in response to LotusPilot

Oh, trust me, I have done everything, including restoring IOS devices.


Today I had it down to just the cable modem with Wifi and one iPad (worked as expected). Had DHCP turned off, and hard-coded the iPad. Worked fine. Turned DHCP back on, set iPad back to DHCP, worked fine. Added a couple of devices and all was well. Had 5 iPads on and two iPhones and at first everything was fine - then after a few minutes the first iPad started showing the same issue again. Gave up and enabled all 27 or so wifi devices and opened a beer instead.


I then put the upstream router back, and moved devices to it. Tried one device with the cable modem wifi again, and all is OK.


Also tried sharing my hard-wired Macbook's network (hard wired to same cable modem), and with a couple of iDevices attached, they work fine.


There could be one device somehow interfering, but only interfering with iOS 13.5.1 devices and tricking them into thinking they are on cellular! All settings have been reviewed and all are correct so far.


Attached screenshot is on my Wifi-only iPad. I'm stumped. It's got to be something unique to me, but caused by a bug. Apple devices think they're on cell.

Jun 27, 2020 2:29 PM in response to AndreTheGeek

UPDATE: It's not my network setup - I removed the router, and went with the cable modem's wifi. Once I had all my devices on its wifi, the problem reappeared. Looking at other forums, others are having different issues, but one seems close - one guy had to turn off his DNS server on his router and hardcode everything on his devices - I don't have that option as I have a lot of devices.


Apple devices running 13.5.1 seem to be interfering somehow with each other. The wifi works, but something is triggering these devices to think that are on cellular. It's almost as if they think they are using a Personal Hotspot, as the behavior is the same.


There's definitely something up with this. I also tried installing the public beta of iPadOS 13.6 on my iPad, but it still has the issue.

Jun 27, 2020 2:42 PM in response to AndreTheGeek

Perhaps with your setup you’ve accidentally configured a double-NAT. If so, this can create all kinds of issues.


If you add a second domestic WiFi router to your network, it is generally essential to ensure that it is configured to operate in bridge-mode.


Setting bridge-mode on WiFi routers upstream of your broadband/cable modem/router will disable Network Address Translation (NAT) on its corresponding WAN port - in addition to disabling its DHCP services. If you fail to do this, both the upstream WiFi router and your broadband/cable router will attempt to NAT its WAN IPv4 Address.

Jun 27, 2020 2:58 PM in response to LotusPilot

It's not that - please see my latest update. It also does it if I take that router down and use my cable modem's wifi without the second router connected. Since the issue wasn't appearing when my iPad is the only device on it, I thought it was my setup, but once I add more and more iOS 13.5.1 devices to the network, it starts the issue again.


It definitely appears to be an iOS 13.5.1 bug. The issue started when I updated my devices. It appears that having several iOS 13.5.1 devices causes the issue. My one iPad with 12.4.7 does not experience the issue, but it is 100% consistent with the 13.5.1 devices. I also haven't ruled out the two Apple TVs. I will pin it down, but the difficulty lies in the fact that adding back devices doesn't trigger it for a while, something gets cached somewhere. I will have to add one device at a time, then reboot things and wait on each.


Also, the second router, it was set up correctly. I can set it up both ways - with one I end up with two networks, the other properly extends it as a single IP network...but both configurations show the same issue. It's not the router. And I have been using this configuration for years and it runs great. It still runs great with iOS 13.5.1, it's just the misleading error about it being on cellular. If I click 'Continue" it works fine.


The only things that fail are Photostream and IOS updates, because they require Wifi, and IOS thinks I'm on cellular.

Jun 27, 2020 3:22 PM in response to AndreTheGeek

The described behaviour is definitely indicative of local network issue.


Whist I have a VDSL connection in place of cable, my own domestic setup is very similar - with multiple upstream WiFi Routers (Apple AirPort Extreme and Express) configured to bridge their respective WAN/LAN ports. I currently use three WiFi network segments - two single and one dual band. Apple client devices are a mix iPadOS/iOS 13.5.1, iOS 12.4.7 and tvOS 13.x in addition to multiple PC and other media client devices.


I cannot replicate the issue that you describe. Consider also that if your explicit problem was an OS bug, we would have seen multiple reports here following the update to iPadOS 13.5.1.


Yes, you have a problem. If you have the capability and technical knowledge, I recommend that you place a protocol analyser on the wired-ethernet segment between your Cable and upstream WiFi Routers.

Jun 27, 2020 3:47 PM in response to LotusPilot

Yup - there's some issue of some kind - and yes, so far it seems to only affect me!


The only thing that has changed though is the IOS updates - and I should not rule out the Apple TV updates.


I maintain it's a bug that for some as yet undiscovered reason, did not show up until iOS 13.5.1 arrived, and does not affect my IOS 12.4.7 device nor any of my other 23 or so devices.


My and my wife's Photostreams both last updated on June 7th. I updated my IOS devices when 13.5.1 came out. My wife was slower to do her two, but possibly around the 7th. One of my Apple TVs updated itself sometime before then, and the other I had to force it, sometime after then.


I've got more detective work to do. Unfortunately I don't have the capability to analyze traffic. But as I mentioned, I can now replicate the issue with just my cable modem's wifi, with the upstream router unplugged. Only when I allow all my devices on does the problem present itself. Perhaps it is one device sending out some kind of packet over the wifi that confuses the other IOS devices. I'm determined to figure it out... but again it is only iOS 13.5.1 devices that consistently believe they are using cellular and another IOS 12.x does not.

Jun 27, 2020 4:09 PM in response to AndreTheGeek

One last shot...


Have you attempted a full restart of your network and client devices - in the correct sequence? If using DHCP, the restart sequence is critical.


1) Restart you Cable Router. To restart, disconnect power for at least 30 seconds - then reconnect power to restart. After your router competes its reboot (this may take several minutes)...


2) Restart each of your upstream WiFi Routers. If they acquire their network configuration via DHCP, consider assigning static IP Addresses, outside your DHCP Address Pool, for each of your network infrastructure devices; this will make your network more stable and predictable.


3) Restart each of your client devices, one at a time, ensuring that each receive a unique IP address from within your DHCP Address Pool; verify that the assigned Gateway IP Address (Router) matches that of your Cable Router.


If this doesn’t resolve your network issue, short of conducting detailed analysis of your network, I’m out of ideas.


I hope this information proves to be helpful in resolving the problem.

IOS/iPadOS 13.5.1 New Bug

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.