Well what else do you expect them to tell you other than they are working on it?

Well, the other part I understood as his personal comment, because no company says that and I am 100 percent sure they didn't do that.

iOS 13.2 beta 2 is out.

Let’s hope for the best.

I don't understand why talking about beta bugs is bad.

If the gm is not out yet, then obviously common sense means that someone is talking about the developer or public beta, because if they check for updates, surprise, they are running the latest. So no confusion there.

Also there is a public beta program, so why are beta bugs considered secretive or inappropriate?

Apple says, nope, don't talk about beta bugs, yet they have a public beta program. How does that make sense?

Also as previously stated, the developer beta can very easily be obtained for free, so technicall there are 2 public betas. I do agree that if you are going to talk about them, make sure you mention it is a beta, and which type, but this whole rule of not talking about beta bugs is ridiculous, especially considering they have a public beta program

Whether it is ridiculous or not, you agreed to it, and that's it. The fact it is ridiculous should be brought up to Apple, but till they agree, it is an official rule, and based on what it says your beta access could be revoked. Of course, as has already been said that probably wont happen, but it's not such a hard rule to respect. Join a private beta testing Vo group, and you are fine to discuss all the bugs and report them. However, let's base it on your example. You were frustrated about the status bar bug, which was fixed in one update and took a week. So it was pointless to mention it to anybody but Apple.

Who complained about it? I saw only one mention of that bug, and it was in this topic. The end call bug will hopefully be fixed soon, but see, even we can't reliably tell if it is or is not fixed, because for me it happens maybe once in 20 calls, while for others it is way more constant. So if you ask me is it fixed in beta 2, I would say I don't know, hopefully it is, have not experienced it in beta 2 yet but had only 2 calls so far.

38 nails it, I think. Instead of telling people not to talk about bugs before a GM release at all, because you have no authority to make them comply to that kind of thing (and policing the internet is impossible anyway, plus the fact that that's unenforceable, which does matter and is relevant), you should explicitly indicate to others to tell us what beta version they're using. Post 34 claimed that users will believe that the beta exists in the released finalversion of the product if you discuss it before a GM release; I posit that the opposite would happen if you suppressed discussion of it: people would assume its not there (when it actually might still be there). Just because you submit feedback to a company doesn't mean the company will do anything about it, and that's assuming that the methods of submitting feedback aren't broken and actually work.

@40, stop being such a Apple fanboy and smell the industrialism.

I will rename the topic and edit post 1 so it is clear this talks about bugs from a beta

Also beta 2 of 13.2 got rid of the end call bug for me

Fuck yeah! Hope it is gone for anyone else on that version as well

@40, uh... because not all users read this thing called a changelog? I'm not 'making less sense'. I'm giving you facts, pure and simple. You cannot stop people from talking about a beta. A beta (in a general sense) is not confidential, either; perhaps Apples betas are confidential but clearly they don't care if people do discuss it (otherwise they'd actually prevent you from talking about it on YouTube). IMO its much better to publicly discuss bugs in betas because it makes the company actually fix bugs because they're practically forced too because of public pressure. A feedback mechanism they can ignore quite easily; but its much, much harder for a company to ignore the pressure of tons of people on various forums demanding that they fix it.

I appreciate that you changed the topic title and edited the first post.
But all I'm really getting out of this is that people who actually depend on there phone day to day really shouldn't be using betas.
And frankly, I thought that would be common sense.
Sounds like you got impatient to try the new version, but even when you saw how fucked it was you didn't revert?  If so, this level of masochism confuses me.
Some of these bugs really are appalling it must be said, particularly the 911 calling bug (I would have stopped using it instantly after that simply out of a moral duty) but it wasn't just the accessibility side of this release that was bad, it was everything.
And even though they shouldn't have released 13.0 to the public in that state in the first place, they did at least pull out the stops to fix it quickly.
Either way, thanks for suffering in order to help report the bugs, that helps all of us.

The fact that Android still cannot copy text from a web page tells you enough about which screen reader is more capable, better not to go in to more advanced things like text detection from images or direct touch for 3rd party apps. VO has this bug which is apparently better in 13.2, but both had major bugs like that. Android had a major bug with web views recently, and these things will happen in both systems and are not a parameter on which one does accessibility better.