Guess you need to delete your dev configuration profile and to enroll for public beta testing on beta.apple.com. But why would you do that as long as builds are the same? Dev builds are just coming a bit earlier if ever.
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.
Apple Seeds Third Betas of iOS 13.3 and iPadOS 13.3 to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Guess you need to delete your dev configuration profile and to enroll for public beta testing on beta.apple.com. But why would you do that as long as builds are the same? Dev builds are just coming a bit earlier if ever.
Just wonder if anyone else is having the App update issue, and if the public beta is also affected.
I think it's part of Apple's privacy plan. People have been forced to look at their phone to unlock it. I believe the courts are still enforcing the right not to give up a password. Once unlocked, theoretically a non-Apple update could be installed that would open up the phone's contents.
while that little thing, of dubious importance, gets addressed, yet since 13.o they still won’t/can’t/don’t address the mismatching of playlist album icons not matching the text name of the playlist. This has to be laziness on Apples part otherwise why not fix it.
macs and iPhones were based all around GUI Interface but now you can’t pick from an icon but have toread a long title.
One thing I wish Apple would do is put the Photos quick launch icon back in the lower left corner of the Camera app when opened from iMessage. I forget when they actually made this change (was it iOS 12?) but it has irked me ever since, and I don’t get it.
When you open the Camera app by itself, the Photos quick launch icon is in the lower left corner, but it’s in the upper left corner when opened from iMessage. And for the matter, put “Done” on the bottom as well.
When you open the Camera app by itself, the Photos quick launch icon is in the lower left corner, but it’s in the upper left corner when opened from iMessage. And for the matter, put “Done” on the bottom as well.
FaceID can handle 2 faces. Let's say I decide to give my child one of those slots so they can play on my phone. Do I really want a 5 year old deciding to install an update? Probably not. Or the other face belongs to my wife. Again, I wouldn't want her to install an update on my phone without my knowledge.
My boys are actually 17 and 22 and have their own devices and I don't let ANYONE else into my phone. But it's a possibility that ought to be considered. Especially with the older TouchID system where you could in theory have 4 other people who could unlock your phone.
The other explanation I've heard is that your passcode is your security. FaceID is a quick and easy way to bypass that security. It's a biometric convenience, not the actual security itself. Which is why you need to enter your passcode after a reboot or when doing something as important as updating the entire OS.
There's some (possibly) lame excuses that may or may not satisfy your curiosity. Honestly, it's a question I've asked myself and I all I could come up with was "extra security". Like asking "Are you sure?" before deleting a file.
When the heck are they going to address the the bugs that are killing XR's????? Since iOS 13 I've got:
• apps that don't respond;
• apps that respond initially, but then freeze;
• apps that don't update in the App Store,
• apps that when they do update in the App Store they still show as not having updated.
This iOS is the biggest balls up ever!!!!!!!!!!!!
• apps that don't respond;
• apps that respond initially, but then freeze;
• apps that don't update in the App Store,
• apps that when they do update in the App Store they still show as not having updated.
This iOS is the biggest balls up ever!!!!!!!!!!!!
That means having an app drawer being there taking up extra space that some might not care for if they really don't use the app drawer.
Well-written and logical explanations. Thanks for answering my question!
[automerge]1574293594[/automerge]
This makes sense, too ... thank you!
By the looks of the testers reports I may actually stay on 13.2.3 as it’s solid and has mail fixes that actually work.
A fair question. But if I’m in the camera app (accessed through iMessage), snap some quick selfies, and want to pick one out to send, you can’t do it one handed like you can when just using the camera app by itself.
It’s one of those weird UI inconsistencies.
I would like to see strict guidelines for exact wording that should be used when saving a photo/video to Photos.
I’ve seen:
Download
Copy
Download Copy
Save Copy
Save Media
Share
etc.
Even Files app is really inconsistent and confusing with its use of Share/Move/Copy.
———
As for app update problems, I had the issue in the first beta but not since. (Rebooting mostly worked.)
I’ve seen:
Download
Copy
Download Copy
Save Copy
Save Media
Share
etc.
Even Files app is really inconsistent and confusing with its use of Share/Move/Copy.
———
As for app update problems, I had the issue in the first beta but not since. (Rebooting mostly worked.)
Delete your dev profile, restart, go to appleseed & d/l the public profile... and bob’s your uncle!
Probably to mitigate some sort of automated attack used by a company in israel that provides hacking tools to government entities.
Apple explains this in their security white paper:
In the case of an Over-The-Air (OTA) software update, the user is prompted for their passcode when initiating the update. This is used to securely create a one-time Unlock Token, which unlocks the user keybag after the update. This token can’t be generated without entering the user’s passcode, and any previously generated token is invalidated if the user’s passcode changed.
There's more details there, if you're curious. Look for Escrow keybag. I pulled the text from the iOS 12.3 white paper. If there's one for 13 I haven't seen it yet.
https://www.apple.com/business/docs/site/iOS_Security_Guide.pdf
I found a way that resolved the apps unable to update issue on my phone, somehow (not sure quite how) and I wanted to mention it. (I have an iPhone 11 Pro Max and the public beta of 13.3).
I decided to file a bug report for the issue with the Feedback app (that's technically what we're supposed to do as beta testers anyway, right, though I'd gotten lazy lately, admittedly). So, I did that and put my phone aside for awhile. A few hours later, I came back and realized I could update the apps again! I figured what may have happened is that, during the process for submitting a report, the Feedback app "gathers relevant files" from your system to send to Apple with the report and something in that process apparently reset something that allowed updates to work again.
So, long story short, if you can't update your apps, try submitting a bug report about it with the Feedback app. It may help. Note that the process asks you to describe the issue by choosing from various drop down menus, and I'm guessing that's part of it. Don't just submit anything, so it looks for the right files.
edit: or maybe Mothandras was right and it was a server-side issue. (They posted while I was typing.)
I decided to file a bug report for the issue with the Feedback app (that's technically what we're supposed to do as beta testers anyway, right, though I'd gotten lazy lately, admittedly). So, I did that and put my phone aside for awhile. A few hours later, I came back and realized I could update the apps again! I figured what may have happened is that, during the process for submitting a report, the Feedback app "gathers relevant files" from your system to send to Apple with the report and something in that process apparently reset something that allowed updates to work again.
So, long story short, if you can't update your apps, try submitting a bug report about it with the Feedback app. It may help. Note that the process asks you to describe the issue by choosing from various drop down menus, and I'm guessing that's part of it. Don't just submit anything, so it looks for the right files.
edit: or maybe Mothandras was right and it was a server-side issue. (They posted while I was typing.)
Nope. Newest beta fixed nothing. Up to 42 and counting.
Nope. I've tried everything but a restore.. which I'm not doing. I guess I'll just never up to date apps. lol.