Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Magic Keyboard & iOS 27

updated to iOS 27 now magic keyboard doesn’t work when using news+ puzzles. Screen actually doesn’t respond at all

5 replies

Remove the iPad from the Magic Keyboard - and carefully/gently clean the smart connector contacts on both the iPad and keyboard with a soft pencil eraser (a drafting-film eraser is ideal). Ensure that the contacts on both iPad and keyboard are dirt and dust free - and all debris from the eraser have been removed - before reconnecting the two.


If you can't connect your iPad to your Magic Keyboard, Smart Keyboard, or Smart Keyboard Folio - Apple Support



If the problem persists, you might be best advised to visit the Genius Bar at your local Apple Store or Apple Authorised Service Provider (AASP) - where the technicians will be able to test and assess your iPad and keyboard:

Genius Bar Reservation and Apple Supp

DoubleUgly04 wrote:
Updated today, but my keyboard is still dead.
At first it only dropped off after closing the iPad, but repeated forced restarts brought it back. Then after one of the closings it stopped working and remains inoperative.
Repeated normal/forced restarts and today’s update made no difference.


As described, your Magic Keyboard for iPad may have an internal fault. Over time, with repeated opening-closing of the Keyboard, the flexible ribbon connection that passes through the hinges can fracture - leading to an intermittent electrical connection. This fault can only rectified by replacing the Magic Keyboard.

Updated today, but my keyboard is still dead.


At first it only dropped off after closing the iPad, but repeated forced restarts brought it back. Then after one of the closings it stopped working and remains inoperative.


Repeated normal/forced restarts and today’s update made no difference.

My Magic Keyboard doesn’t respond at all after update. I was using it to make the update so it was working perfect. There has to be a way to fix it, or am I waiting for another update?