How to fix iOS 8 Unicode Messages crash bug

Here's what you need to know about preventing and recovering from the iOS 8 Unicode crash bug.

While Apple is working on a fix for the bug that causes Messages and notifications to crash iOS 8, there are several things you can do right now to help prevent your iPhone, iPad, or Apple Watch from being affected, and to try to recover if you've already been affected.

1. Unless you have reason to believe you're a target, you probably only need to do this until your friends' attention span lapses and they move on to the next prank.
   
2. We've had luck with these methods. They may or may not work for everybody. Other people may or may not have had luck with other methods, up to and including a restore with Messages or notifications disabled. Make sure you let us know in the comments what's worthing for you!
   

How to prevent crashes from the lock screen

1. Launch the Settings app from your or iPad iPhone Home screen.
   
2. Tap on Notifications.
   
3. Tap on Messages.
   
4. Toggle Show on Lock Screen to OFF.
    
   
   

How to prevent Apple Watch crashes

1. Launch the Apple Watch app from your iPhone or iPad Home screen.
   
2. Tap on Notifications.
   
3. Tap on Messages.
   
4. Tap on Custom.
   
5. Toggle Show Alerts to OFF.
    
   
   

How to clear notification center to prevent crashes

If you've already received the bad Unicode string maliciously or as a prank, send yourself or have someone else send you a clean message to the same app.

1. Hold down the Home button to launch Siri.
   
2. Say "Send a message to [name]".
   
3. Say "Send it" or tap Send.
    
   
   

You can also use the Share Sheet.

1. Launch Photos from your iPhone or iPad Home screen.
   
2. Tap on any Photo.
   
3. Tap on the Share button.
   
4. Tap on the Messages icon.
   
5. Enter the recipient.
   
6. Tap Send.
    
   
   

That should fix the notification crashes, but you still won't be able to open any conversation or screen that contains the bad string.

If you've been affected by the bug, or found any other fixes, please let us know.

Nick Arnott contributed to this article.

Continue reading...