My belkin boost charger 3 in 1

Hello Nieper,

Thank you for reaching out to Apple Support Communities.

We were able to find this from Belkin:

"If you are experiencing alignment or non-charging issues with your phone, this article will teach you a few fixes that you can try.

1. Make sure that the wireless charger is connected properly to a power outlet.

2.  When you position your phone on the wireless charger, you should see a notification on the screen that tells you it’s charging. If you don’t see a notification or message, try to adjust the position of your phone.

3.  You can also try to remove your phone case. Though wireless chargers are designed to work with most cases, some cases have metals to make them more durable or compatible with magnetized phone holders which may cause intermittent charging.

4. Another common issue with wireless charging is the misalignment of the phone on the charging pad or stand which causes the phone to not charge. Here are some of the symptoms of improper alignment:

• The phone will not charge.
• There is an error light on the wireless charger.
• There is no light at all on the wireless charger.

To fix these issues, try to move your phone slightly on the wireless charging pad or stand to align it correctly. The location of the charging coil may vary depending on the model of your phone. You can check with your phone's manufacturer for tips on how to properly align your phone on a wireless charger."

More details can be found here: Troubleshooting wireless charging issues

If you are still having issues, we would recommend reaching out to the manufacturer directly, as they support the product and not Apple.

You can do so by going to Welcome to Support

Hopefully this helps.

Cheers!

Hi Support. I have the same problem. All of the above has been tried. The phone charges with a cable, but not with my Belkin 3 in 1 since the last update. This is an apple issue from the update. I've experienced issues with this charger with my apple watch series 7 and had to wait for an update for that to work again. I hope this bug is being addressed from this last update.