Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Does anyone else get random resprings on their 17 Pro / Pro Max?

I haven’t been seeing a lot of resprings on my iPhone Air, but I’m getting a lot on my M4 iPad Pro. Sometimes just resizing an app crashes the system.
 
  • Wow
Reactions: macfacts
miguel7734 said:
Hello, I have a similar problem. I bought an iPhone 17 Pro Max in October and, a month later, unexpected restarts began. I requested support at the Apple Store in Madrid, but they didn't find any problems. I was suggested to restore the phone from my Mac and make a backup to iCloud. However, the problem persisted. After requesting technical service again, I was informed that it was a hardware problem and they changed my Logic Board last week. After two days, the problem returned and I requested a replacement iPhone, which arrived last Thursday. Yesterday, the phone unexpectedly restarted again and, after factory resetting it today, it restarted twice more. Does anyone know how to solve this problem? The replacement iPhone is new, with zero charge cycles, but it arrived with several problems. Apple is responsible for not being able to use my phone normally for two weeks, and I'm worried that this will happen to my wife at any time. I have tried several solutions, such as restoring WhatsApp without backup or photos, but the problem persists.
Click to expand...
I have this problem too, from november my iphone 17PM restarted like 10 times. Not much but frustrating. I read many situations like yours with replacement iphones: now it seems really obvious that is something related to an app or the account itself. Hope one day it will stop, but for now it’s not as costant to worry me.
 
bluewave83 said:
I have this problem too, from november my iphone 17PM restarted like 10 times. Not much but frustrating. I read many situations like yours with replacement iphones: now it seems really obvious that is something related to an app or the account itself. Hope one day it will stop, but for now it’s not as costant to worry me.
Click to expand...
In theory, with yesterday's update it has been solved it was a problem when generating iOS textures. We will have to try to see if it is true that it has been resolved, recognized the error at least it is and I have already contacted a YouTube channel with 1 million followers that will address the issue to see if it can put pressure

Confirmation of ImageIO error (CVE-2025-43532)

Apple has already updated its security database. The bug we saw in your log (EXC_BAD_ACCESS in ImageIO) is officially resolved by an "improved memory limit check". This means that the "hole" through which the process escaped and caused your mobile phone to turn off has been blocked.
 
  • Like
Reactions: Ferrd
miguel7734 said:
In theory, with yesterday's update it has been solved it was a problem when generating iOS textures. We will have to try to see if it is true that it has been resolved, recognized the error at least it is and I have already contacted a YouTube channel with 1 million followers that will address the issue to see if it can put pressure

Confirmation of ImageIO error (CVE-2025-43532)

Apple has already updated its security database. The bug we saw in your log (EXC_BAD_ACCESS in ImageIO) is officially resolved by an "improved memory limit check". This means that the "hole" through which the process escaped and caused your mobile phone to turn off has been blocked.
Click to expand...
But it’s weird only few of us have this bug… i’m really curious to know WHAT triggers it
 
miguel7734 said:
In theory, with yesterday's update it has been solved it was a problem when generating iOS textures. We will have to try to see if it is true that it has been resolved, recognized the error at least it is and I have already contacted a YouTube channel with 1 million followers that will address the issue to see if it can put pressure

Confirmation of ImageIO error (CVE-2025-43532)

Apple has already updated its security database. The bug we saw in your log (EXC_BAD_ACCESS in ImageIO) is officially resolved by an "improved memory limit check". This means that the "hole" through which the process escaped and caused your mobile phone to turn off has been blocked.
Click to expand...
Searching on internet this bug is solved with 26.2 but it’s not because i had 2 resprings with .2
 
Hello

I have spoken to Apple and I have reported all the errors with technical details. At first they offered me a replacement, but seeing that I have insisted on the well-written errors and with technical data, they have told me that they would review the case and that, if it seems a software problem.

They seem a little lost. Tomorrow they will call me again, although I have demanded that they pass me with the engineering department.

At first I slipped the option to request a replacement again, which I refused. I'll keep you informed.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back