No, I don't think they are changing the code for tomorrow, but I also don't think they release these betas for no purpose. They want to collect data on things they have already fixed and determine stuff that might be a showstopper in the wild. And I don't agree that nothing reported now will have any impact on the release version of iOS 13. Clearly there are some major issues with automations in Shortcuts and with the ETA feature in Maps, hence their removal from the current betas. My guess is that each has a fighting chance of making it back in before release, as we are still about 2-3 weeks away from the GM (if not a week longer). I would say, however, that Dev Beta 6 is probably the last point at which anything other than a showstopper has a chance of being addressed.Might well be tomorrow or Wednesday, but do you really think Apple iOS developers are frantically changing the iOS 13 code right now for supposed tomorrow’s beta version? Unless there is a major show-stopping bug, the logs and error reports submitted now might get addressed in iOS 13.1 + releases, if we are lucky.
[doublepost=1565622535][/doublepost]
Of course they don't do that. Its a feedback loop. They dogfood it internally (after stress testing it on simulators) and then release it to the public (incluiding non-Apple developers). That last stage (which we see) either validates the internal work or discloses issues that no amount of internal testing will turn up. That info is then fed back into the process. When it gets fed back in probably depends on how serious it is.
