How'd it do that? (/sarcasm)
But yet you let it have access to your production data. I see.
[doublepost=1567097108][/doublepost]
What's amusing is that it's something to complain about, vs restoring a backup and moving on.
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.
What's New in iOS 13.1 Beta 1: Share ETA and Shortcuts Automations Return, Plus More
- Thread starter MacRumors
- Start date
- Sort by reaction score
How'd it do that? (/sarcasm)
But yet you let it have access to your production data. I see.
[doublepost=1567097108][/doublepost]
What's amusing is that it's something to complain about, vs restoring a backup and moving on.
Restoring a backup still makes for a stressful moment, takes away from your time, and also means you don't have the latest version (unless you backup crazy frequently).
OR... those of you having a lot of issues are the minority. You seem to think your experience somehow is the general one when you say things like "...it is factually unequivocally unstable" when you have no brand set of data. It's been fine on my XSMax since b3 (didn't try 1 or 2).
It always amuses me that people who see a lot of issues don't, when others say "we don't see that" try the dirt obvious troubleshooting step of doing a clean install.
Actually, I filed a bug with Apple before anything else, and they responded. Turned out to be a glitch in my account at their end and all data was fine on iCloud.com although it did disappear for a while which is what concerned me.
After verifying it all, I logged out of iCloud on all devices and logged back in, restoring all syncing and now it’s back to normal.
The point of the post - and this followup - is for anyone else who might have a similar issue to find some solace and/or a solution. But I guess it also attracts unhelpful people like you. I can live with that.
My backups are just fine but they go nowhere near my beta machines - not the main backup anyway. Restoring from a backup won’t fix the syncing problems and these sorts of issues need to be fixed before this all goes ‘live’.
Really important stuff I need synced is via DropBox during these betas, not iCloud Drive, but I can’t put *everything* in DropBox and I need to test with my real data - I’d rather have my data messed up before my users’ data is messed up.
I can see why your username has ‘pos’ in it now. Apt.
[doublepost=1567110206][/doublepost]
Oh, that’s going to be the case next year, although I need to see how I can access all the data, etc. via CloudKit Dashboard if it’s not my Developer Account - not sure I’ll be able to see the data from a dummy account?? It’s the main reason I keep it simple with a single developer account - and I’m a solo developer.
Realistically, I think I’ll skip future betas entirely and wait until full release - so many APIs are unpolished, unfinished and poorly documented that it makes it almost impossible to have something ready for iOS 13 release date anyway as the goalposts keep shifting. Now I see why so many bigger developers often leave new-iOS features out for 6 months or more in their apps.
It’s the first time this has ever happened in all the years of beta development testing - I never expected the OS on devices to mess with iCloud content so badly and then propagate it to non-beta devices. I don’t mind my beta devices getting messed up though. What would be useful would be for Apple to sandbox the iCloud Drive somehow for testing.
Of course I have backups so nothing is lost and I’ve discussed this with Apple and it’s sorted again (see other reply to the less helpful ‘pos’ guy).
Last edited:
Because this is how software development works. Writing software specially at this scale means you will always create bugs, no matter how long you work on it. They could spent four more months “polishing” the original release then in the process break things that worked before. Apple released for example iOS 12.4 quite recently only to release afterwards 12.4.1 because 12.4 broke something that previous iOS versions had patched. Basically a new iOS version was less secure than an old version. Software development isn’t that easy as many people think.
That should never be necessary, though. I don’t know how widespread those issues are (the betas have been mostly OK for me; this one still seems to have some Springboard crashes and Mail weirdness), but if 1% are affected, are you going to tell 10 million users to do a clean install?
Yeah, a sandbox would be nice.
(Or simply a second user account, but that’s never going to happen on iOS.)
I’m guessing your budget is kind of limited being a solo developer, but I’d still recommend an old iPhone for betas.
(I say all that despite living the no-risk-no-fun lifestyle of having the beta on my main iPhone with my main iCloud account…)
One thing that hasn't worked in all of the betas, and I haven't seen mentioned anywhere is the following ..
Earlier I could disable all sounds for messages and set custom sounds for the contacts I still wanted a audible notification for, and it worked fine. Now when I disable sounds for messages, it just disables them everywhere irrespective of your custom notification settings for a contact.
I was under the impression that its' just the beta, and they'll put it back at some point. But now seeing it amiss from the 13.1, is just sad. There's now no way to have audible notifications for only a few select contacts, while disabling it for everyone else - all the other messengers I use have it - WhatsApp, Telegram, etc.
Earlier I could disable all sounds for messages and set custom sounds for the contacts I still wanted a audible notification for, and it worked fine. Now when I disable sounds for messages, it just disables them everywhere irrespective of your custom notification settings for a contact.
I was under the impression that its' just the beta, and they'll put it back at some point. But now seeing it amiss from the 13.1, is just sad. There's now no way to have audible notifications for only a few select contacts, while disabling it for everyone else - all the other messengers I use have it - WhatsApp, Telegram, etc.
In retail versions I'd agree. But when you install a beta you're by definition installing software that has bugs. If you have issues and a lot of people on a message board such as this say "Huh, not seeing that at all" then you can 1) whine about it like a little child, 2) report the issue and then do clean install to see if that fixes it or 3) Decide you don't want the issues that come with installing a *beta* and revert back to the last release.
If someone chooses (1) above we're not obligated to stroke their ego, though. It's axiomatic among support people and anyone else with good problem solving skills that if someone is experiencing issues which the vast majority are not seeing it's an issue with that person's setup. It's valuable to know that (hence why we're asked to report things) so that Apple can track down what might be happening in those edge cases but once you've done that it's silly to continue to whine about it without trying things like a clean install that might fix it.
And some people probably have niche apps (corporate stuff, little used apps, etc) that DO have issues with the beta OS and that a clean install won't fix. Again, report that but if it's really that bad, revert to retail once you've reported it.
Last edited:
yes in the homes app you can do all that. The control center widgets for quick select are limited that you can't scroll over to a second page. Makes it rather useless to me unless. Id like pages to be able to scroll over on both accessories and scenes.
This is true, but it's also true that iOS 13.0 final is likely ~3 weeks away, if that, and some of the issues haven't seen progress in the branch we can actually look at. It's possible that there exists an internal branch where Mail can actually keep its folders refreshed without having to swipe back and forth, or a branch where Springboard crashes less, or one where the keyboard doesn't suddenly take up three quarters of the screen. Or that those issues are being fixed as we speak and will make it by release. It's increasingly unlikely, though.
Apple usually (including with iOS 13 beta 1) also distinguishes between developer distribution and public beta distribution. 13.1b1 was shipped to both developers and public beta users, so they seem to think it's fit enough to be tested and more-or-less used by millions of people.
Still resprings a lot. Mail still not good. Safari still has issues with a lot of web sites that use pulldown menus. Bad betas this year.
Hello.
13.0 is coming out. 13.1 on Sept 30th
https://www.apple.com/newsroom/2019/09/apple-introduces-dual-camera-iphone-11/
