I don’t think that’s a bug, I think it’s working as intended. I don’t use Standby, but I use the Sleep Focus/schedule and it works the same there. It was like that in iOS 16 too.Anyone know if the bug where your alarm gets really quiet if you happen to sleepily glance at your phone on its stand when it's going off when standby is active and "Attention Aware Features" is on (word soup!) has been fixed?
I was nearly late for work due to this bug, but do like the other perks of having "Attention Aware Features" turned on.
FYI, mine's not 100% either. Doesn't freeze as much, but still freezing. Very annoying. So you're not alone. Hoping they are still tweaking for the next beta.One of the KEY FIXES of 17.2 is WiFi speeds. That was my point, not that "this beta sucks" - it was a selling point of 17.2 was around the improvement to network speed. Which in my case was a network degradation.
![]()
iOS 17.2 fixes Wi-Fi slowdowns and connectivity issues, Apple says - 9to5Mac
Since the release of iOS 17 last month, a number of iPhone users have complained about Wi-Fi connectivity problems. Thankfully,...9to5mac.com
The issue with small size dynamic text leading to corrupt UI in the settings app is really annoying.
How can this stuff ship like this?
I’ve noticed a few messages end with “How can this stuff ship like this?”
Ask Craig Federighi
frederighi@apple.com
Yep, same conditions here.Same for me. Got our first snowfall this morning.
The issue with small size dynamic text leading to corrupt UI in the settings app is really annoying.
How can this stuff ship like this?
I have emailed him before about a cryptographic issue and had a response.
I don't want to be bugging people, pun intended, but it's getting a little ridiculous.
I could give you 5 examples of sloppy UI in iOS from the top of my head.
Don't they have basic unit testing?
It hasn’t shipped. It’s beta 1.
Do you maintain millions of lines of code with ridiculously fast iteration times?
File the bug. If it’s on their critical list they’ll fix it.
It probably WAS working as intended before standby came along. But it should not lower the volume while in standby because if you happen to be sleeping with your eyes open a bit (more common than you think), facing your phone on your nightstand, the alarm won't go off at full volume to wake you up.I don’t think that’s a bug, I think it’s working as intended. I don’t use Standby, but I use the Sleep Focus/schedule and it works the same there. It was like that in iOS 16 too.
I have emailed him before about a cryptographic issue and had a response.
I don't want to be bugging people, pun intended, but it's getting a little ridiculous.
I could give you 5 examples of sloppy UI in iOS from the top of my head.
Don't they have basic unit testing?
How I use my iPhone 14 Pro, I don't up against any UI glitches.
And Im a Creative working in UI, web design, Graphic etc, so quite intense with all this stuff.
Would you like to see some examples?
Would you like to see some examples?
It feels like a bad year for iOS unfortunately. I bet Apple have moved a load of Dev resources onto Vision Pro…some of the bugs do seem to be quite amateurish.It started in 17.1, I just cannot believe it's still in 17.2 beta or otherwise, it's so fundamental.
Yes.
I did, this type of bug is completely unacceptable, it's fundamentally flawed rendering of text, not some esoteric workflow.
I understand what you’re getting at now, it’s a very good point you make 👍🏻.It probably WAS working as intended before standby came along. But it should not lower the volume while in standby because if you happen to be sleeping with your eyes open a bit (more common than you think), facing your phone on your nightstand, the alarm won't go off at full volume to wake you up.
Basically an unintended consequence of the phone now being on a stand, facing you in bed, rather than laying flat on the nightstand. So yeah, maybe not a "bug", but definitely an issue.
All they have to do is make this "quieting" feature not kick in if standby is active; that would fix the problem.
👍👍👍 I am always amazed at those who make blanket statements that THEIR issue is earth shattering and affects all users and all devices. I suspect that the main issue is not with the device. I’ve had a fair number of issues that I sometimes see referred to in a few rare posts, and sometimes none at all. They are usually fixed in future releases, sometimes a long time afterward. I actually got an email from AppleSeed recently stating that an issue I reported over a year ago in ios 16 should be fixed in the current beta. And it was. I guess I could have just told everyone who stated they didn’t have this issue that they were just using their device improperly, as I’ve seen some do.Once again I need to issue the following reminder:
Yes, there are bugs in Apple’s software. However, they do not affect all users or all devices. Apple will triage those bugs based on the number of users/devices affected and/or the severity of the bug.
The most unfortunate thing is that you had to wait for over a year for your bug report to be fixed. This does not bode well if/when the bug is a troublesome one. Oh well though, software eh.👍👍👍 I am always amazed at those who make blanket statements that THEIR issue is earth shattering and affects all users and all devices. I suspect that the main issue is not with the device. I’ve had a fair number of issues that I sometimes see referred to in a few rare posts, and sometimes none at all. They are usually fixed in future releases, sometimes a long time afterward. I actually got an email from AppleSeed recently stating that an issue I reported over a year ago in ios 16 should be fixed in the current beta. And it was. I guess I could have just told everyone who stated they didn’t have this issue that they were just using their device improperly, as I’ve seen some do.
That particular one was not mentioned anywhere on any forum and I had asked multiple times over that year. In Feedback Assistant it had always been displayed as no other reports. So I was surprised to get the email and that it had finally been fixed. Obviously it was something minor and not affecting many, if any, others. Nothing is perfect and sometimes you just have to accept it and work around it, or ignore it.The most unfortunate thing is that you had to wait for over a year for your bug report to be fixed. This does not bode well if/when the bug is a troublesome one. Oh well though, software eh.
Precisely, just part of life I guess.That particular one was not mentioned anywhere on any forum and I had asked multiple times over that year. In Feedback Assistant it had always been displayed as no other reports. So I was surprised to get the email and that it had finally been fixed. Obviously it was something minor and not affecting many, if any, others. Nothing is perfect and sometimes you just have to accept it and work around it, or ignore it.
Turns out this was an Apple issue (confirmed with engineering).Numbersync / WiFi calling has failed with 17.2.
Worked fine up until 17.1.
4 hours on phone with ATT. Disabled/reenabled WIFI calling and numbersync for apple.
Replaced eSIM. Absolute nightmare.
It’s been an issue before, but never this bad. It’s completely broken.