That's disappointing to hear. I wanted an automation that would send me a notification when my commute is over X minutes.
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
That's disappointing to hear. I wanted an automation that would send me a notification when my commute is over X minutes.
Nah the guy you quoted has a point. There are a LOT more features in iOS now. I’ve been following iPhone/iOS since 2007 and easily forget what this OS is capable of.
I didn’t know you could move multiple apps at once until a few months ago. There’s a lot of little things now.
I’m not complaining at all, but the gestures and shortcuts amp up every year.
Exactly, or one that automatically does things like read out the weather, start navigation, send a message, etc. All we get is a button on the lock screen to invoke it manually which is the dumbest thing in the world.
You know what a beta is for, right?
Keep in mind that it's not fully opaque, so its actual huge will vary. Sometimes it's more brown-ish, sometimes more yellow-ish. Here's a few image results:
Your new wording makes more sense — it does seem brighter than before (and it was, indeed, a bit too washed out before).
I’m on iPad OS too. It’s not a great experience yet; frequent crashes too. Speak selection is crashing Safari with one voice but not another. Go figure.
Can’t update any app either, so I’m guessing a new PB must be right around the corner (it better be!).
Last edited:
Yes, so stupid. Have reported that multiple times. Let‘s send them as much feedback as possible.
Shortcut automation is fake. It's not automation, it's a reminder. You need to start the reminder manually.
Freaking Apple. I was so excited to use NFC with shortcuts. Got so excited to see automation for shortcuts was added back expect for the NFC tag portion. Apple. WTF
Yes, I think/hope everyone who installed the Betas knows they are betas but as we get closer to release they should be more stable. As someone who continues to find some puzzling bugs and unexpected behavior I'm really worried about the state of 13.0 if it is already locked. Perhaps the GM will surprise me but I think it still feels very rushed and half-baked.
Yes, I know that it is beta and that is what beta means. But the point of this process is to refine the software and get it ready for release. Unless Apple has been holding back bug fixes, that doesn't seem to be the case here.
That makes zero sense.
Clearly, they moved some features originally slated for 13.0 to 13.x, which isn't unprecedented (e.g. AirPlay 2).
Having fewer new features in 13.0 helps them focus on reliability instead.
[doublepost=1566935393][/doublepost]
It'll probably come back later.
13.0 is shaping up to have a poor reliability reputation, so postponing features or even canning some (for now) is the right move.
Well I guess we will have to agree to disagree, been testing iOS betas and Mac OS betas as far back as I can remember, even before iOS was released... I have had to revert back to stable versions many times in iOS (ios11)and have no problem admitting when it’s a disaster.. I can state that this is far from it , general bugs always get into final releases .. maybe it’s the device your using or how it was initially installed ... sorry you’re having enough bugs that it makes it unusable... I’m having the exact opposite experience, as I’m sure a majority of people are having , seems to me the only people that post stuff are the people who are having problems, that seems to be the minority....
Good post. Everyone knows the point of the beta program is to find bugs but as we get into early September the betas become what is going to ship on these phones. Saying "it's still a beta" is technically true but completely ignores the fact that the prevalence of bugs this late is a bad sign for what is going to be released in a couple weeks (how could it not be?).
iOS 11 was one of the worst software releases I've ever experienced and those beta threads were full of people defending Apple close to public release by saying "Of course there are lots of bugs, it's the beta! Stop complaining!". Then what happened? They released an absolute garbage OS that took months of constant updates to become pleasant to use.
Yes, but the argument is that betas are for finding bugs that only can be found in the real world, say with custom software or setups. Easily reproducible bugs that can be identified in the development process should be fixed before that, so that testers can concentrate their efforts on these hard-to-find bugs.
In a good development process, betas should be a carefully considered milestone that allows for QA and feedback, demonstrating how all the pieces work together, not a dump-in-progress of current development.
To give an extreme example, if they released a beta that deleted all your data ever 5 minutes, you would never be able to find out that birthdays on leap years crash the calendar when syncing to Exchange server 2013.
luckily for you... there are still a few flip phones on the market
BS—as soon as I turn off my wake up alarm, all lights in my house is on, my fan is on and coffee is served in the kitchen.
seems like chaos in the iOS development team with two betas. Something isn't right
I wonder if the code Apple removes / omits from the dev betas to not give away upcoming products has any impact on stability, and if switching developers over to 13.1 with those references still omitted allows Apple to start locking down the GM with everything included and not have to deal the Rambo guy from 9to5mac digging through the code to post leaks.
(Side note: I’m honestly surprised Apple hasn’t pulled 9to5’s access to events yet considering the blacklist Gizmodo got put on for buying the iPhone 4 left in the bar and publishing info on it. There’s definitely a fine line difference between simply reporting on leaks and one of your employee’s being the source of the leak and breaking the developer NDA.)
The thing people in this thread need to understand about software testing and patch releases is that feature development of iOS 13.0 stopped months ago. Internal testing started and more recently, external testing started.
During that time, the developers didn’t sit and wait for bugs. They started on the next part of the backlog under iOS 13.1. It may surprise you but they likely are already coding iOS 13.2. They do this while they fix bugs for iOS 13.0 and iOS 13.1.
On many software projects, changes made to upstream branches (i.e. fixed made to iOS 13.0) merge automatically into downstream branches (ios13.x). However on an operating system this likely only happens periodically due to the complexity and difficulty in merging the two code bases.
It’s possible that iOS 13.1 has bugs in it which have already been fixed in the latest beta of iOS 13.0 and won’t be merged into iOS 13.1 until 13.0 hits GM.
I get that it’s unprecedented for a patch release to hit beta for Apple before the .0 release goes GA but it’s really not that uncommon in software dev.
Finally, the commenter who said ios 13.1 will be taking the release date of ios 13.0.... that doesn’t speak ill of iOS 13.0, rather it means iOS 13.1 got done ahead of schedule. If true it means that the internal checks of the 13.1 features are complete and they feel confident that they can deliver them by the 13.0 release date. Personally I think that’s highly unlikely. But if true it’s not a bad thing.
During that time, the developers didn’t sit and wait for bugs. They started on the next part of the backlog under iOS 13.1. It may surprise you but they likely are already coding iOS 13.2. They do this while they fix bugs for iOS 13.0 and iOS 13.1.
On many software projects, changes made to upstream branches (i.e. fixed made to iOS 13.0) merge automatically into downstream branches (ios13.x). However on an operating system this likely only happens periodically due to the complexity and difficulty in merging the two code bases.
It’s possible that iOS 13.1 has bugs in it which have already been fixed in the latest beta of iOS 13.0 and won’t be merged into iOS 13.1 until 13.0 hits GM.
I get that it’s unprecedented for a patch release to hit beta for Apple before the .0 release goes GA but it’s really not that uncommon in software dev.
Finally, the commenter who said ios 13.1 will be taking the release date of ios 13.0.... that doesn’t speak ill of iOS 13.0, rather it means iOS 13.1 got done ahead of schedule. If true it means that the internal checks of the 13.1 features are complete and they feel confident that they can deliver them by the 13.0 release date. Personally I think that’s highly unlikely. But if true it’s not a bad thing.