Maybe this update has been withdrawn due to unforeseen bugs.Somebody wake up the guy at Cupertino responsable of uploading the itunes ios firmwares lol.....
Maybe this update has been withdrawn due to unforeseen bugs.Somebody wake up the guy at Cupertino responsable of uploading the itunes ios firmwares lol.....
They aren't looking at your pictures.. that's just the typical scare mongering at work. They are running an algorithm on pictures that you upload to their servers. Only if it is flagged as potential CP as a result of that operation (that you control) will anyone ever look at it.But its not like they are looking at your pictures, there is millions of apple users, why would they look at your pictures?
Aha, yes, it looks like it, and even then, just iPad Mini 6Wasn't RC2 iPadOS 15.1 only?
Both iOS 15.1 and iPadOS 15.1 come with build number 19B74. For iPad Mini 6 it comes with version 19B75.
It was one of the most useful features as well.Thank you for confirming! It's a little sad that the feature I was looking forward to the most was just to have the feature they broke, but that's okay haha
Thanks! I had to do a full restore; no idea what the issue was. Such a pain...The only other suggestion via google is a DFU restore. A quick search of the forums is from another T-Mobile user.
https://forums.macrumors.com/thread...update-failed-on-tmobile-anyone-else.2276108/
Once you build this, then it's a much smaller ask when the FBI knocks and says, we want you to search for these hash values too (which would not be related to the child porn images). That would be a fight Apple would likely lose. It opens a big door.
Some of the world's most esteemed cryptographers and computer scientists wrote a paper about "The Risks of Client-Side Scanning" ( https://arxiv.org/pdf/2110.07450.pdf ). Read the Summary, there are really compelling reasons why this is very bad for everyone.This is the real problem. Scanning for CP is not bad, in and of itself. In fact, it’s a good thing. However it does mean it can be expanded.
Additionally, the push to do this on device is problematic. I expect data on their servers to be processed by them for all kinds of purposes. Data on my device is mine. They say it’s to “respect privacy” but it actually does the opposite.
Yep, But given that the storage including photos has changed back to being accurate I assume it might be re-indexing and will re-appear soon.Anyone else notice the “shared by” section of photos in the for you section is missing now?
Wife’s 13 Pro Max still has issue.What model is your iPhone? We should be listing the model for bugs like this, we can tell what models are affected. The user below with the 12 Pro said the update fixed his storage reporting error.
I with you on that. They gave me a paper card with all the info on it that's required but it can't be converted to a digital card. If I would of went to CVS, Safeway or other pharmacies I would of had the opportunity to have it digitally. I scanned the card and keep it in the notes app but hardly as convenient as having it in the wallet.I wish my state offered vaccine cards.
I didn't try the RC, but it's messed up my Exchange calendar. Meetings showing at the wrong time, wrong day, wrong duration etc. Now completely useless. This is a pretty bad fault.I hope this is a different version than the RC. The exchange calendar integration is messed up on the iPhone 13 Pro. Crashes, shows the wrong time requiring a restart. MacOS struggles the same way with Calendar and O365 appointments. Rooting for better from Apple. I am rarely one to complain, but it is terrible.
My issue was, my iPhone 13PM not waking the screen (call still active) when you move out from the ear position. I have to double press the sleep/wake button to wake up the screen. Then when you put the phone near your ear, the screen will turn off, and you move out of the position again, now this time the screen will back on.This update didn’t fix the stuttering issue when waking up my iPhone 13 PM (with Tap to Wake toggled off). Really frustrating to be honest.
And it was working fine...Thanks! I had to do a full restore; no idea what the issue was. Such a pain...