Not having that issue, although sometimes the doc is completely missing, but it’s rare enough not to be too much a problem, and I usually can bring up search and launch the app that way. Then again, I’m on arm12x iPad and not an M1.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 16.3 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
The new architecture doesn’t support an iPad as a hub. It was in the release notes.
Not sure this is fixable, and I rarely say that. I’d get an AppleTV or a HomePod, either can be a hub.
Could the location being Greece be messing with the spelling? If the locale is American English, I’d send it feedback.
And I had my data go out earlier and had to do 2 re-starts to get it back online again in a strange turn of events..😳
I’ll second this. There should be little reason to have “Limit IP Address Tracking” turned on on your home network, as you’re likely not tracking yourself with the telemetry. That could be messing with it.
These days, at home, they’re tracking the home routers public v4 or v6 address. So when my sister in law searches for a new swimsuit, everyone in the house starts seeing ads for swimsuits.
The limit IP Address tracking is intended to make it difficult for stores, venues, etc. to profile you each time you return there my randomizing your MAC address. Not really needed on your own home network.
You have your terminology confused. The "Private wi-fi address" is what's used on a local network to obscure your device's identity in stores and such. On a home network, there's really no need for a private Wi-fi (MAC) address.
"Limit IP Address Tracking" is for internet sites and it has value even on a home network.
Did we just get a new iCloud Terms and Conditions with this RC?
Was checking PR was off.
Got the old Read and Agree
Was checking PR was off.
Got the old Read and Agree
Pretty good with Lockdown Mode enabled on 13 mini. Installed via IPSW, and in the words of Ronald McDonald (and @Pearsey )…I’m lovin’ it
🤡Wow…horrifying that Apple’s QC continues to lack so awfully. Perhaps we’ll finally see a fix in 16.4?
I don't think they will fix this in the next update. There is no information on the status of the fix for this issue. Most people don't see the difference because games aren't important to them. I play wild rift professionally and I can't play this game on iphone 14 pm for 4 months now. fps is not stable and there are stutterings. iPhones without promotional displays feel much more stable, smoother without fps dropsWow…horrifying that Apple’s QC continues to lack so awfully. Perhaps we’ll finally see a fix in 16.4?
I tried to turn on Advanced Data Protection from my iPhone 14 Pro but I got a prompt to remove my 2015 rMBP from my list of registered devices before I could proceed. 😔
Attachments
Yep, popped up on my Mac earlier but haven’t gotten anything on iPhone.
I think the poster’s point was that 16.3 RC May have automatically applied the new Home architecture. Previously you had to elect into it.
You’re confusing Private Wi-Fi Address with Limit IP Address Tracking which is very different.
The latter protects you from building a profile on you using your browsing history by hiding your IP address from both ISP and the website you’re visiting. You need it enabled regardless of the network you’re using if you care about privacy.
Private Wi-Fi Address randomizes MAC address that stores use to track you and is not needed on your home network.
I have a phone on iOS 15, and the Home app still works so I guess my other phone (16.3) didn't do an upgrade.
I have no home hub though (no Apple TV or homepods).
Maybe not all that many people have the issue... my notifications come up with rounded corners just fine.
Had data drop out twice in the past two days, once after I was in a garage with poor reception and walked out and another time after leaving home Wi-Fi. I still had service and the 5G icon was still there, but loading pages was extremely slow. Resolved after toggling airplane mode
Not sure if this is RC specific or something else.
13 ProMax - iPad Pro 11 - Apple Watch Ultra
All share the same calendar - Apple stock calendar
Twice this morning I have received a calendar update for a meeting, one a time change and the other a cancellation.
In both cases, the alert Notification shows up on the watch, then the iPhone, then the iPad. All are about a minute apart.
The calendar items are from an Exchange account - push.
Why the difference in alert timing and in that order? Not making sense. Did not have this in previous beta
Looking for thoughts before I file a feedback.
AW on 9.2 WiFi only
13PM on RC
iPad on RC
13 ProMax - iPad Pro 11 - Apple Watch Ultra
All share the same calendar - Apple stock calendar
Twice this morning I have received a calendar update for a meeting, one a time change and the other a cancellation.
In both cases, the alert Notification shows up on the watch, then the iPhone, then the iPad. All are about a minute apart.
The calendar items are from an Exchange account - push.
Why the difference in alert timing and in that order? Not making sense. Did not have this in previous beta
Looking for thoughts before I file a feedback.
AW on 9.2 WiFi only
13PM on RC
iPad on RC
Yes, I know that, you misread my post. Im saying I believe the new Home architecture was updated with 16.3RC release as it has now disabled my one home without an atv or HomePod as the hub while all the other homes with an ATV work fine. In the previous betas (16.3b2 and previous) the iPad still worked but gave you a warning that upgrading the architecture wasn't possible until you added a hub at that location.
What iPhone do you use?Wifi issues (connected but unable to browse, Wireless CarPlay breaking up/losing connection while driving down the road) starting in 16.2... 16.3 Beta 1 actually was problem free then nothing but problems in 16.3 Beta 2, I confirmed the RC still has the issues. Feedback reports submitted each time. I guess I wait and see if 16.4 will fix this.
