Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This happened to me last night. The shut down sound woke me up. I said what the? Then I remembered this article. I have a 15 Pro. It shouldn’t be doing this.
 
iPhone 14 Pro, running iOS 17.1 (21B5066a)
It shut itself off for several hours last night.
 
Happened a couple of days ago to me too.

iPhone 12 Mini. Shutdown for 4 hours from 2am to 6am.

When I awoke, my phone was asking for my SIM Pin, which only happens after power up restart.
 
Likely I said earlier, try "rebooting" your iPhone and see if the problem persists. Then go on a once-per-week manual reboot schedule and see if that solves the problem.
 
Do you happen to have an Apple Watch? If so, check System Services under your watch’s Settings > Privacy > Location and then use your iPhone to disable whichever toggles you don’t want on (you might have to first flip ‘on’ and then ‘off’ on iPhone end) so that settings across the two devices eventually match up. This finally got my system location services to stay where I wanted them before I recently bit the bullet and ditched my Watch altogether.
I checked and the settings there are the same as I previous configured. Thanks for the tip though.
 
  • Sad
Reactions: iLuddite
First the green hue lcd screen software that broke lcd screens, then the throttling battery life, then the purple lines on screen, then the violent camera shaking, now turning it off.
 
I’m finally retired. Besides my wife wakes me up. A good slap on the side of the head “WAKE UP” works pretty good. lol
 
  • Haha
Reactions: Stevez67
My phone yesterday morning was off, charged to 100% instead of 80 as set up and very, very hot.

Another masterclass from apple software dev team. Bunch of incapable people. I wonder when someone in there will get the wake up call and start taking action. They are absolutely incompetent.
 
  • Like
Reactions: That70sGAdawg
Well, when I read this article yesterday, I was so happy my phone was not doing this. The kiss of death! Last night I joined the club. I decided to report this to Apple so the numbers reporting would build into a more important issue for them. They did admit they are aware of and working on this. They requested that they call me to gain more info. I said yes. They called. System said "Press 1 to accept this call now". Sadly, I pressed '1' and -- NEW ISSUE -- my phone would not send any tone. I could not accept the call. I pushed all the numbers and nothing. They called back a few minutes later and this time my phone did generate the tones. So, on that call, I reported another issue of randomly the phone not generating the tones. So I got two issues for the price of one. iPhone 14 Pro iOS 17.0.3

I guess I better go out and buy a wind-up alarm clock and a cheap wired phone to back up this $1000.00 device.
 
  • Like
Reactions: cjgrif
I think it might be related to optimized charging. I used „stop charging at 80%“ for the first 2 weeks on my new iPhone 15 Plus and changed it to optimized charging for exactly one day / night. I did not think much of it but it was the same day I was wondering why my iPhone asked me for my passcode to activate FaceID in the morning. I switched back to „stop charging at 80%“ the next day and it hasn’t happened again since
Related to charging but not optimised. It happened to my iPad Pro 10.5 when I left it to charge overnight, but it doesn’t have the optimised charging option - too old.
 
Last night i plugged mine in and i can say it did not shut down or reboot and the battery graph is not showing any blank gaps in between (14ProMax).
Although around 11.35pm my phone while it was charging did the magsafe lock noise (when you attach something) and the screen lit up for a few seconds and im charging via lightning cable.

Never seen or noticed it do that before.

EDIT: Forgot to add as well that when my shut down happened the 2 nights ago and that i just remembered to check now the auto iOS updates for all 3 options were turned on, i always had them to off.
 
  • Like
Reactions: addamas
My 13 Pro did this on Monday night for about four hours, again after reaching 100% charge. Latest iOS 17. Hasn't done it since. The torch did randomly stop working earlier though, but thats back.
 
By the way, I’m also having the opposite problem. I powered off my old iPhone 13 Pro and plugged it in to fully charge it. Then at some point, possibly hours later, it randomly turned itself on. I noticed because my iMessage notifications started dinging from both phones.
 
My phone yesterday morning was off, charged to 100% instead of 80 as set up and very, very hot.

Another masterclass from apple software dev team. Bunch of incapable people. I wonder when someone in there will get the wake up call and start taking action. They are absolutely incompetent.
Working from home has ruined Apple software...
 
My iPhone X has been doing this for quite some time on iOS 16.

Quite frequently, I wake up to no notifications, no wifi or cell, but my alarms always function. The widgets I have on the Lock Screen are blank or blocked out. "Enter your password after restart" or some nonsense, I unlock it, it connects to everything, I go about my day.

Thought it was a fluke and have been ignoring it entirely. I now have to wonder if some app was causing it or some variation on this iOS glitch. Wife's identical X on the same iOS release on the same dual charger never exhibited a single similar issue.
 
More of that solid apple software at work. It just works* lol. Get more of those WFH bugs in the software...
 
  • Like
Reactions: eekram
Same here. 13 mini, woke up to my phone asking for my SIM pin which only happens after a reboot. Never seen that before and thought it was weird. Thank goodness it turned back on, I use my phone alarm exclusively.

Hope they get this sorted soon.
 
Working from home has ruined Apple software...
I work from home and am much more efficient because of it. Maybe it has more to do with teams being overworked due to increasing productivity expectations?

I can’t speak for Apple/software development specifically, but where I work we are pushed to the absolute limit of what can be done, with the fewest employees possible. This year alone our workload increased 25% with no increase in FTEs (and a 2.5% raise despite the inflation). At some point things will start to break…

Personally I’m burnt out, but I know anywhere else I go in my field it’s the same situation
 
Can you imagine how much energy this is saving?! 💚

apples-mother-earth-cringe-v0-yxjgq05mkvnb1.png
… unless your alarm did not go off, you overslept, and as a result had to drive your car to work rather than ride your bike … 😊😊
 
Working from home has ruined Apple software...
They must be working from home since 2012 then..
I honestly think that contributed to it but there is a clear lack of talent and leadership in the software team.
They have the absolute best in the hardware department but they destroyed the software completely since the passing of Steve pretty much.

I am absolutely convinced that at apple they don’t use apple devices. I can’t otherwise explain how some bugs can go unnoticed for several years.
 
Apple has reached out to me. They call it a "circuitry arrest"

In basic:
It is typically performed by lowering iPhone temperature to between 18 °C and 20 °C (64 and 68 °F) and stopping the CPU and GPU. This state is called deep hypothermic circuitry arrest. At such low temperatures most iPhones can tolerate the clinically dead state for up to 30 minutes without incurring significant internal damage. Longer durations are possible at lower temperatures, but the usefulness of longer procedures has not been established yet.
 
  • Haha
Reactions: VulchR
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.