iPhone XS Max XS Max Crashing Issue

[BigTomCallaghan]

Hi all,

I am having an issue on my new XS Max where, when attempting to launch certain apps, the screen will go black and the phone will restart. This is a replicable issue when opening Lyft, Pokémon GO, Google Maps, Uber, or taking a Snapchat. As you can see it appears as though when a third-party app is trying to access and utilize my location is a trigger for this behavior. However, other third-party apps work as intended and can launch and use my location.

The most interesting part of this however is it happens no matter how my phone is set up:

I have used an iOS 11 backup from my iPhone X, an iOS 12 backup, and a full-blown DFU restore on a clean phone and this situation persists.

I haven’t seen any other mention of this in the forums or on the ‘net and am hoping someone can help or has had a similar issue. REALLY disappointing start for a $1100 piece of hardware - for the record my X is still running everything fine on iOS 12... Perhaps this becomes the year I finally skip on the new hardware.

EDIT: Forgot to mention that, in the case of Lyft or GMaps, if I tap the screen rapidly and try to interact with the app before it goes to the black screen, it sometimes launches and works normally. Super weird.

 

[WilliamG]

I can’t fathom the logic behind skipping hardware because you got the one bad unit. If this is doing it on a DFU restore, exchange the device. That’s it. You’ll be on your merry way.

 

[BigTomCallaghan]

I can’t fathom the logic behind skipping hardware because you got the one bad unit. If this is doing it on a DFU restore, exchange the device. That’s it. You’ll be on your merry way.

Because I’ve already spent more time than it is worth on this issue and the time is at more a premium to me than the money, quite frankly. Taking the time for a trip to the Apple store and going through the process with a specialist to exchange the device sounds awful to me personally.

I am more blown away at how this could still be happening after a full DFU restore and clean install. Doesn’t strike me as a hardware issue, but who knows I suppose...

 

[WilliamG]

Because I’ve already spent more time than it is worth on this issue and the time is at more a premium to me than the money, quite frankly. Taking the time for a trip to the Apple store and going through the process with a specialist to exchange the device sounds awful to me personally.

I am more blown away at how this could still be happening after a full DFU restore and clean install. Doesn’t strike me as a hardware issue, but who knows I suppose...

I still don’t get it. You just return the device, buy a new one, and restore from a backup in mere minutes.

 

[Deguello]

Because I’ve already spent more time than it is worth on this issue and the time is at more a premium to me than the money, quite frankly. Taking the time for a trip to the Apple store and going through the process with a specialist to exchange the device sounds awful to me personally.

I am more blown away at how this could still be happening after a full DFU restore and clean install. Doesn’t strike me as a hardware issue, but who knows I suppose...

If it doesn't strike you as a hardware issue, why would this be the year you skip the hardware?

It sounds like you've eliminated software as a possibility. What else is left?

 

[Breitling65]

I got application crash yesterday while running Zello on my XS Max, total crash I have to reenter all my settings in Zello which is a lot of work.

 

[peejay1977]

I don't get people's rage at having an issue with something that cost alot of money. I agree that as the price for something increases you'd expect a more premium device but manufacturing issues still occur. Plus it's still the same software (pretty much) regardless of device.

It's like buying a £1,000,000 Bugatti and expecting that it'll NEVER have a problem.

Sometimes it happens, I don't see what relevance the hardware has to the equation. You could just have got a duff unit, it happens.

 

[BigTomCallaghan]

I don't get people's rage at having an issue with something that cost alot of money. I agree that as the price for something increases you'd expect a more premium device but manufacturing issues still occur. Plus it's still the same software (pretty much) regardless of device.

It's like buying a £1,000,000 Bugatti and expecting that it'll NEVER have a problem.

Sometimes it happens, I don't see what relevance the hardware has to the equation. You could just have got a duff unit, it happens.

No rage here, just frustration. As mentioned above time is at a premium for me. I don't want to goof around with this for another 3 hours of restoring and backing up. People get so defensive on here, lord... Expecting my $1100 piece of hardware to work properly with big-time applications out of the box != expecting to "NEVER" have an issue.

 

[Mlrollin91]

Pokémon Go is a horribly coded app. There are memory leaks all over the place. I have this game crash 5 times a day irrespective of the device I’m using. You should not use that app as a benchmark. I can intentionally make it crash upon launch every single time.

If you phone is respringing, it’s more likely than not a hardware problem, either with RAM or processor.

 

[BigTomCallaghan]

Pokémon Go is a horribly coded app. There are memory leaks all over the place. I have this game crash 5 times a day irrespective of the device I’m using. You should not use that app as a benchmark. I can intentionally make it crash upon launch every single time.

If you phone is respringing, it’s more likely than not a hardware problem, either with RAM or processor.

LOL ain't this the truth. I was more surprised with Lyft/Uber/GMaps as the coding tends to be of a [much] higher quality, in my experience...

 

[peejay1977]

No rage here, just frustration. As mentioned above time is at a premium for me. I don't want to goof around with this for another 3 hours of restoring and backing up. People get so defensive on here, lord... Expecting my $1100 piece of hardware to work properly with big-time applications out of the box != expecting to "NEVER" have an issue.

Not being defensive, I have no issues with my phone....

And I get your frustration I really do, and I get time is important. Bug's occur, why it's not doing it for other people I don't know but the cost of your device seems irrelevant, unless it's a hardware issue, which you've stated you don't believe it is. So whether it's a 3yo iPhone 6S or a brand new XS Max, the cost isn't really a factor.

The development of the OS and the apps is the same regardless. The Photoshop Express app is poorly coded to cope with the Max and it's a pain to use, but sometimes it happens.

To be fair your issue is much worse than my issue with Photoshop but it happens. In your shoes I'd be seriously pee'd off but it happens whatever the device or platform, hence the Bugatti analogy. You "seem" to be linking the impact on your wallet with the development effort of app developers and that just seems odd to me.

If you've tried with a clean iOS image, no backup etc then it suggests it could be a hardware issue, you sound like a smart guy and have eliminated all the obvious causes like latent bad code or data.

 

[cbarnes3121]

cool

 

[BigTomCallaghan]

Not being defensive, I have no issues with my phone....

And I get your frustration I really do, and I get time is important. Bug's occur, why it's not doing it for other people I don't know but the cost of your device seems irrelevant, unless it's a hardware issue, which you've stated you don't believe it is. So whether it's a 3yo iPhone 6S or a brand new XS Max, the cost isn't really a factor.

The development of the OS and the apps is the same regardless. The Photoshop Express app is poorly coded to cope with the Max and it's a pain to use, but sometimes it happens.

To be fair your issue is much worse than my issue with Photoshop but it happens. In your shoes I'd be seriously pee'd off but it happens whatever the device or platform, hence the Bugatti analogy. You "seem" to be linking the impact on your wallet with the development effort of app developers and that just seems odd to me.

If you've tried with a clean iOS image, no backup etc then it suggests it could be a hardware issue, you sound like a smart guy and have eliminated all the obvious causes like latent bad code or data.

This is my thought too - I would really like to use my backup so I guess it's a relief that this appears to be HW related. I may simply call for the return package so I can send this one back and buy another online. If that one doesn't work then I'll stick with my X one more year...

 

[peejay1977]

This is my thought too - I would really like to use my backup so I guess it's a relief that this appears to be HW related. I may simply call for the return package so I can send this one back and buy another online. If that one doesn't work then I'll stick with my X one more year...

Yeah, I'm not sure what else to suggest, if you've set up as a new phone then that usually clears any chance of it being anything left behind.

The only thing you could do is perhaps see if it does it on wifi or cellular only etc, maybe run some tests or just install the bare minimum apps and see. Although if time is limited that might not be an option.

I work in software development so the need to know would be killing me haha

 

[BigTomCallaghan]

Yeah, I'm not sure what else to suggest, if you've set up as a new phone then that usually clears any chance of it being anything left behind.

The only thing you could do is perhaps see if it does it on wifi or cellular only etc, maybe run some tests or just install the bare minimum apps and see. Although if time is limited that might not be an option.

I work in software development so the need to know would be killing me haha

I DON'T work in development and the curiosity is still killing me haha... It does on both cellular and Wifi, I know that. So far, Lyft, GO, Uber, GMaps, and Snapchat (ONLY after taking a photo, presumably when the location-based filters are loading) have the issue. I feel it HAS to be something with 3rd-party location requests based on that information, but again, who knows...

 

[peejay1977]

I DON'T work in development and the curiosity is still killing me haha... It does on both cellular and Wifi, I know that. So far, Lyft, GO, Uber, GMaps, and Snapchat (ONLY after taking a photo, presumably when the location-based filters are loading) have the issue. I feel it HAS to be something with 3rd-party location requests based on that information, but again, who knows...

I use GMaps and Snapchat out of that list and no problems for me, but I'm struggling to think of something that might make a difference. Have you got any restrictions enabled? I guess not if you've started fresh.

Whats your usual setup process? Do you normal heavily configure the system settings once you've signed in etc? Or are you more like me, sign in to my iTunes account, change a few general UI based things and then get installing apps?

 

[BigTomCallaghan]

I use GMaps and Snapchat out of that list and no problems for me, but I'm struggling to think of something that might make a difference. Have you got any restrictions enabled? I guess not if you've started fresh.

Whats your usual setup process? Do you normal heavily configure the system settings once you've signed in etc? Or are you more like me, sign in to my iTunes account, change a few general UI based things and then get installing apps?

On the new install I didn't touch hardly anything as I wanted to get right to loading these apps to see if the issue persisted, which obviously it did. On my backup I don't have any sort of abnormal restrictions in place with regards to location... It definitely strikes me as a memory leak situation since it only occurs as these apps are trying to load / immediately after load but as mentioned in my OP Edit, if I rapidly tap the screen and try to interact with the app while loading / right after load, they will generally launch in full and perform as normal.

 

[peejay1977]

On the new install I didn't touch hardly anything as I wanted to get right to loading these apps to see if the issue persisted, which obviously it did. On my backup I don't have any sort of abnormal restrictions in place with regards to location... It definitely strikes me as a memory leak situation since it only occurs as these apps are trying to load / immediately after load but as mentioned in my OP Edit, if I rapidly tap the screen and try to interact with the app while loading / right after load, they will generally launch in full and perform as normal.

Very odd dude! I'm out of suggestions unfortunately aside from upgrading to iOS 12.1 beta to see if it miraculously cures your issues

 

[BigTomCallaghan]

Yeah, thanks for talking it through - just going to order another and start the return process with this one I suppose.