iPhone 13 Bugs/Issues: Some new ‌MagSafe‌ Wallet owners are unable to get ‌Find My‌ to connect

At the Apple iPhone 13 launch event, the company also launched an updated version of the MagSafe leather card case with the built-in Find My function. However, some iPhone 13 users are facing a new issue to use the “Find My” function of the MagSafe leather card case.

JOIN APPLE ON TELEGRAM

According to a post on Reddit (via MacRumors), some users are unable to get the “Find My” pop-up window when connecting the MagSafe leather card case to the iPhone. This problem seems to particularly affect the iPhone 13 series models, but there are some complaints from iPhone 12 users too.

Check some responses from the users:

I had 3 calls with customer support and we were able to get it working for my iPhone 13 pro max. This is what worked: they told me to go to Settings > General > Transfer or Reset > Erase > Erase Network Settings. The phone restarted, and after restarting and attaching the wallet to the back of my phone, the animation popped up and wallet is now in my Find My app!

A Reddit user EndlessApology was told by Apple Support to put his ‌iPhone‌ into Device Firmware Update (DFU) mode to reinstall the OS using a Mac.

Got my own Wallets today and immediately had this issue with both my 13 Pro & Pro Max. Spoken to Apple tech, and followed what they said and it fixed it. Put the phones into DFU mode, and reinstall the OS and Firmware. Set the phone up again without doing any recovery. Once set back up, pop the wallet on and it’ll pop up after about 5 seconds, and let you pair to Find My. After that, if you need to, reset the phone on the device itself, and restore from back up in set up. Sorted 🙂

According to the Reddit post, Apple is aware of this problem, so it may be fixed in a future update.

At present, users who want the MagSafe leather card case to work immediately should try to reset the network settings option. If it is not successful, use the DFU method to reinstall iOS 15. Or you can wait patiently for Apple to push the follow-up iOS 15.X update to fix it.