iphone xs max charging

I explain why this is occurring at the link below; it is not a bug.

Lightning-Based Charging May Not Work in iOS 11.4.1 or Later If Your Device Has Been Idle over an Hour or You Did Not Use a Cable Within the past Three Days

It's hard to say; if it's an Apple charger and cable, it may be a software issue.

If it's a third party charger, it could be hardware, related to the new security feature that requires you to authenticate before connecting to a computer via the Lightning port when the device is asleep.

Hey guys I have been having this issue as well and been to apple and swapped out about 3 iPhones xs max gold and it’s happening on all of them. This most resent one I have does the same thing also and it won’t charge when the display is asleep usually after about 5+ seconds of it being asleep and then you plug the lighting cable in and it won’t charge. It doesn’t happen always but happens enough to notice. When the display is on and you plug the cable in the issue doesn’t seem to present itself. We even tried this on one of the apple employees phone who has the same one and guess what it did the same thing. After about 5+ seconds of the display being asleep and you plug it in it won’t charge but you remove it and then plug it back in and it will charge. Like I said it doesn’t happen always but it will happen. My sibling has an iPhone XS max silver and the same issue is present. We concluded at apple store that it’s a software issue and apple will more than likely be rolling out some sort of update in the upcoming weeks.

I have an XS Max and the charging logo comes up instantly and the screen wakes as soon as the Lightning cable is plugged in, each and every time, no matter how long the screen has been asleep.

That doesn't mean it's not software, but it also means the issue is not universal, so I would make sure you notify Apple Support directly of your issue if the Apple Store didn't log the issue with Apple for you.

Yeah same. I tried to dock for an iTunes backup and it just sat there. I figured it was the Trust rules for USB, but it would only work once unlocked and docked.

After Unbox Therapy’s video I did some tests and it really didn’t like it until unlocked.

I’m wondering whether deep sleep is just too aggressive or if the motion engine takes it out of deep sleep when you handle it the right way and not if the wrong way.

One to look out for if they ‘fix’ this issue, is that the idle battery lifetime doesn’t drop. I’d take a bit of fiddling over battery life any day.

Same problem here but i have to charge my phone every other day and it takes about 6 hours to charge from 24%. I now charge it overnight. Hopefully the next update to ios 12 will fix the battery usage and charging problems.

I’d say this explanation has merit. I poked around and, yeah, I think mine would fall into this category., although it appears not all.

What that means though is the warning box that used to appear doesn’t anymore. That in itself makes a feature utterly confusing. Sounds like a simple fix to go in an update.

@William Kucharaki: Thanks for explaining this issue in detail. For example, the suggestion, turning on the USB Accessories option in settings does not work out quite well for me; at least it is very unreliable (my iPhone XS sometimes refuses to charge after let's say 15 minutes of inactivity, too). But a double tap always forces the phone to start charging. A raise to way sometimes works, sometimes not. I only use the bundled cable and charger. To be said, I did not try to hard reset my device -- maybe that's also worth a try?

It seems like that the custom handshake between charger and device is not implemented correctly in power management, particularly in regard with the "new" security feature of iOS.

As for now, I can live with the issue, as I use wireless charging or quickly activate the display before charging via cable. So at least there is a workaround and a good hope that Apple is able to fix this via Software Update.

Some people have reported that the charging indicator does not come up if the screen is asleep; others do not have the same issue.

Why can't you easily replicate it? Doesn't it happen every time you connect a cord, or is it just sometimes?

Try a different cable just to rule that out; sometimes the contacts on a cable can get dirty or wear a bit leading to the issue you describe (flipping the cable over also sometimes works.)