iOS 17.4 Beta 1 ― Bug Fixes, Changes, and Improvements

[Quille]

As this seems to be affecting nobody else it may be a hardware issue.

This can't be a hardware problem, because before the update on iOS 17, everything flew and worked smoothly, everything started on the day after the update from 16.7.1 to 17.1, so the software update led to a hardware problem? Moreover, the sliders in the control center began to flicker immediately after the update from 17.1.2 to 17.2...

Apparently this is a new Apple method with planned obsolescence, I am very disappointed.

 

[Quille]

That doesn’t rule out a hardware issue. Actually, it kind of reinforces that hypothesis.

How can a software update lead to hardware-related problems? everything worked stably on ios 16, the design of the phone was not changed, it all started after the update on iOS 17

 

[Quille]

This can't be a hardware problem, because before the update on iOS 17, everything flew and worked smoothly, everything started on the day after the update from 16.7.1 to 17.1, so the software update led to a hardware problem? Moreover, the sliders in the control center began to flicker immediately after the update from 17.1.2 to 17.2...

Apparently this is a new Apple method with planned obsolescence, I am very disappointed.

This problem is also observed on the 14th and 15th generation models, I'm not sure about xr, 11, 12, on the contrary, they are the most stable on ios 17, as far as I know from my studies of the forums

 

[gwhizkids]

This can't be a hardware problem, because before the update on iOS 17, everything flew and worked smoothly, everything started on the day after the update from 16.7.1 to 17.1, so the software update led to a hardware problem? Moreover, the sliders in the control center began to flicker immediately after the update from 17.1.2 to 17.2...

Apparently this is a new Apple method with planned obsolescence, I am very disappointed.

You know you had my attention until you went with the planned obsolescence nonsense. Goodbye.

 

[Quille]

You know you had my attention until you went with the planned obsolescence nonsense. Goodbye.

Well, what is it then, like unplanned obsolescence, when my device works perfectly on the previous system, but on the new one after the update it gets a decrease in productivity, battery life and broken functions. What is it called? The new version of iOS 17 caused physical damage to the CPU during the update.

In that case, does it turn out to be a hardware problem too? I will surprise you, it started too after the update from 16 to 17, before that everything was perfect

 

[Populus]

How can a software update lead to hardware-related problems? everything worked stably on ios 16, the design of the phone was not changed, it all started after the update on iOS 17

Correction: if other users are reporting this exact behavior on their phones, it might be an iOS 17 bug. If this is the case, the only thing you can do is wait patiently until Apple fixed it.

There was a bug, I think on iPadOS 13, that after a certain combination of actions, it caused a restoring/reboot of the iPad. Nobody was aware of it because nobody did with their iPads what I was doing in order to crash it. It implied having a PDF and a text editor in split screen, with the PDF on the right side, IIRC, while screen recording, and then pushing down the Control Center. It was such an unique situation, that despite reporting it several times, I had to wait several updates, until one of the last iPadOS 13 updates, to have it fixed.

I’d recommend you to patiently wait, if it’s not addressed in the following updates, it will be with iOS 18, most certainly. All we can do is report it and wait. Good luck.

This problem is also observed on the 14th and 15th generation models, I'm not sure about xr, 11, 12, on the contrary, they are the most stable on ios 17, as far as I know from my studies of the forums

If your experience, or perception, is that iOS 17 works better on older devices, that goes against the idea of planned obsolescence that you mentioned earlier. Following the planned obsolescence theory, the newest devices should be the ones that work well with the latest operating system.

 

[Populus]

The new version of iOS 17 caused physical damage to the CPU during the update.

Look: from what I see, it looks like iOS 17 is just buggy, let’s hope that by the release of 17.4 they have managed to crush most of those bugs, otherwise we’ll have to wait until later updates or even iOS 18. Rumors said that they spent a week solving many minor bugs. Hopefully they will offer a more polished experience soon.

 

[Quille]

Correction: if other users are reporting this exact behavior on their phones, it might be an iOS 17 bug. If this is the case, the only thing you can do is wait patiently until Apple fixed it.

There was a bug, I think on iPadOS 13, that after a certain combination of actions, it caused a restoring/reboot of the iPad. Nobody was aware of it because nobody did que their iPads what I was doing in order to crash it. It implied having a PDF and a text editor in split screen, with the PDF on the right side, IIRC, while screen recording, and then pushing down the Control Center. It was such an unique situation, that despite reporting it several times, I had to wait several updates, until one of the last iPadOS 13 updates, to have it fixed.

I’d recommend you to patiently wait, if it’s not addressed in the following updates, it will be with iOS 18, most certainly. All we can do is report it and wait. Good luck.


If your experience, or perception, is that iOS 17 works better on older devices, that goes against the idea of planned obsolescence that you mentioned earlier. Following the planned obsolescence theory, the newest devices should be the ones that work well with the latest operating system.

I am very surprised that a company like Apple has not been able to fix some 2-3 bugs with the user interface for six months, which significantly affects the user experience.
I probably won't wait for ios 18 and switch back to android, since Apple has such an attitude towards its users that they force them to settle for operating system bugs for a year.

Try to cause this problem yourself now:
1. Lower the volume to zero via the buttons
2. Increase it to 50% through the control center
3. Lower it back to zero via the buttons
4. Pull the volume slider down. there will be a short flicker of the slider, it will return to the value it was at for half a second after completing the second step.

I don't understand how you can break something so fundamental...

As for the lags of the control center, start opening or closing it when moving from a room with poor light to a room with good illumination, animation will start playing at 10-20 fps

I used the planned obsolescence simply because at first I thought that this was it, especially since many people write about it on reddit

 

[Quille]

View attachment 2343476

Look: from what I see, it looks like iOS 17 is just buggy, let’s hope that by the release of 17.4 they have managed to crush most of those bugs, otherwise we’ll have to wait until later updates or even iOS 18. Rumors said that they spent a week solving many minor bugs. Hopefully they will offer a more polished experience soon.

According to one unconfirmed source, the flashing of the sliders is still not fixed in 17.4 beta 1, especially since the bug with the notification center from 16.0 still exists in 17.3. To play it, you must have notifications from two different applications, after which you need to pull them down to hide them and swipe them out a buggy animation will occur up, the lower notification will jump up slightly, merge with the upper one, after which it will return to its place, if you want, I can provide a screen recording. I've already written to apple about this, they still haven't reviewed any of my appeals since November(

Upd: Screen record

 

[contacos]

I‘m from the EU and I can’t see any changes lol. Even the settings app is exactly the same as 17.3, I was hoping to see some alternative App Store settings

I got an initial on-boarding pop up asking me to set a default browser. However, once I clicked it away, there is nothing in the Safari settings or anywhere to change it later.

 

[DeanL]

Has anyone noticed that when unlocking the iPhone even without touching the camera button activates the green indicator in the control centre indicating that the camera app is actually using the camera? It has been since the time of iOS 16 that I have noticed this phenomenon and, to date with the various releases of iOS 17, it still persists

Start fresh and pay attention to the apps you are reinstalling. One of them could be the culprit.

 

[BugeyeSTI]

I am very surprised that a company like Apple has not been able to fix some 2-3 bugs with the user interface for six months, which significantly affects the user experience.
I probably won't wait for ios 18 and switch back to android, since Apple has such an attitude towards its users that they force them to settle for operating system bugs for a year.

Try to cause this problem yourself now:
1. Lower the volume to zero via the buttons
2. Increase it to 50% through the control center
3. Lower it back to zero via the buttons
4. Pull the volume slider down. there will be a short flicker of the slider, it will return to the value it was at for half a second after completing the second step.

I don't understand how you can break something so fundamental...

As for the lags of the control center, start opening or closing it when moving from a room with poor light to a room with good illumination, animation will start playing at 10-20 fps

I used the planned obsolescence simply because at first I thought that this was it, especially since many people write about it on reddit

Just tried using the instructions you provided to recreate the bug multiple times and my 15PM on 17.3 doesn't have this issue. It is a unique set of inputs that's for sure. How did you even find it? I always adjust volume using the side buttons and occasionally control center but never the way you're describing

 

[Broken Hope]

I am very surprised that a company like Apple has not been able to fix some 2-3 bugs with the user interface for six months, which significantly affects the user experience.
I probably won't wait for ios 18 and switch back to android, since Apple has such an attitude towards its users that they force them to settle for operating system bugs for a year.

Try to cause this problem yourself now:
1. Lower the volume to zero via the buttons
2. Increase it to 50% through the control center
3. Lower it back to zero via the buttons
4. Pull the volume slider down. there will be a short flicker of the slider, it will return to the value it was at for half a second after completing the second step.

I don't understand how you can break something so fundamental

Who actually uses their device this way?

You can create an obscure bug by changing the system volume in a way that nobody who uses the device in a normal way does.

 

[dk001]

Apple put the functionality there for a reason.
He found a bug.

Now the waiting begins…

 

[FILIPSN007]

I found out this bug during playing Wild Rift. It happened in landscape mode. But just once.

 

[gwhizkids]

Apple put the functionality there for a reason.
He found a bug.

Now the waiting begins…

Disagree. That’s like saying that because Apple made the iPhone a physical object capable of being thrown that Apple is somehow liable if you throw the phone against a wall.

People who come up with these ridiculous Rube Goldberg-like scenarios to induce a bug and then run around screaming about how Apple doesn’t pay attention to quality deserve the reaction they get in this forum.

 

[dk001]

Disagree. That’s like saying that because Apple made the iPhone a physical object capable of being thrown that Apple is somehow liable if you throw the phone against a wall.

People who come up with these ridiculous Rube Goldberg-like scenarios to induce a bug and then run around screaming about how Apple doesn’t pay attention to quality deserve the reaction they get in this forum.

That makes little sense. Apple did not create the iPhone as a throwing object. Least I hope not

There are multiple ways to change the volume. This Apple added as a set of features. Buttons, Control Center, Sliders (some apps and Home Screen prior to DI).

This is an odd bug triggered by a sequence of events. Lord knows I have found a few in my day. Now we file a Feedback and just wait.

 

[Broken Hope]

File it all you want, it will end up near the bottom of the priority list.

 

[Quille]

Disagree. That’s like saying that because Apple made the iPhone a physical object capable of being thrown that Apple is somehow liable if you throw the phone against a wall.

People who come up with these ridiculous Rube Goldberg-like scenarios to induce a bug and then run around screaming about how Apple doesn’t pay attention to quality deserve the reaction they get in this forum.

If you don't have this error, then what should I do to make sure that everything is fine with me. I am currently on 17.4 beta 1 and I have the same problems. Unsurprisingly, the 15th generation does not have this problem)

 

[Kal Madda]

Well, I guess now they will have access to the Safari extensions. One thing I didn’t like about making a website a web-app, is that you couldn’t use Safari Extensions on them.

But I think that’s not the most optimal change. Web-apps shouldn’t open in Safari. We’ll see

I really was hoping they’d add the web app system they just introduced with macOS that can turn ANY webpage into a web app, instead of it having to be specifically coded to support that. Several sites I want to open in their own window don’t do that currently, but on macOS, any web app will open in its own separate window. Maybe they’re working on implementing that in iOS 17.4, and that’s why the existing system is encountering bugs? I can only hope. It’s going to be a major downgrade for me if all of my web apps open in the browser which wastes precious screen real estate, and can’t be it’s own independent window like a norma app. 🙁

 

[Quille]

Just tried using the instructions you provided to recreate the bug multiple times and my 15PM on 17.3 doesn't have this issue. It is a unique set of inputs that's for sure. How did you even find it? I always adjust volume using the side buttons and occasionally control center but never the way you're describing

I managed to reproduce the problem on 1 try, do you see an error here?

 

[Quille]

I take it you don't see anything strange here either
Bug 1
Bug 2

Please open your eyes and try to reproduce it because of you Apple will never fix it

 

[gwhizkids]

That makes little sense. Apple did not create the iPhone as a throwing object. Least I hope not

There are multiple ways to change the volume. This Apple added as a set of features. Buttons, Control Center, Sliders (some apps and Home Screen prior to DI).

This is an odd bug triggered by a sequence of events. Lord knows I have found a few in my day. Now we file a Feedback and just wait.

My point is that simply because steps can be physically taken, virtually no one has a reason to go through that particular key sequence. Just because it can be done, doesn't mean that it would normally be done by 99.999% of users.

I, for one, don't want Apple engineers chasing down ridiculous bugs submitted by users who are clearly trying to find bugs for their own 15 minutes of fame. Count me out.

 

[Quille]

Disagree. That’s like saying that because Apple made the iPhone a physical object capable of being thrown that Apple is somehow liable if you throw the phone against a wall.

People who come up with these ridiculous Rube Goldberg-like scenarios to induce a bug and then run around screaming about how Apple doesn’t pay attention to quality deserve the reaction they get in this forum.

I didn't try to find this error, I just use my device more often than you do and at 100% of its capabilities

 

[Quille]

My point is that simply because steps can be physically taken, virtually no one has a reason to go through that particular key sequence. Just because it can be done, doesn't mean that it would normally be done by 99.999% of users.

I, for one, don't want Apple engineers chasing down ridiculous bugs submitted by users who are clearly trying to find bugs for their own 15 minutes of fame. Count me out.

This is a basic user interface element, why shouldn't it be fixed? Just because you don't use your phone like that?

In all 10 years of using Android phones, I have not seen such ridiculous errors in the basic functionality of the operating system as on iOS