-
All replies
-
Helpful answers
-
Sep 24, 2014 2:39 AM in response to Beavis38ghzby Ocean20,In settings/general/spotlight search do you have messages ticked?
-
Sep 29, 2014 5:23 PM in response to Beavis38ghzby mohanp,See the following thread. They have a solution that fixes it.
cannot search messages after upgrading to iOS8!!!
Thanks to user Joelrubi
His suggestion (which worked for me) is as follows:
"
JoelrubiSep 27, 2014 11:38 AM Re: cannot search messages after upgrading to iOS8!!!
Re: cannot search messages after upgrading to iOS8!!!in response to ILuvApplesAfter relentlessly switching languages back and forth out of sheer anger and desperation (Lol), it finally worked for me. But I did something different at the last time. After switching to Spanish, I waited 30 seconds. Then toggled off and on Messages in Spotlight. Then while still in Spanish, did a search and it started to search of all 1.3GB of Messages worth that I have. Switched back to English, started to search, it seems to restart the indexing all over again, but rebuilt pretty fast and now all is back to normal - meaning I can search all of my 1.3GB of Messages again. I know, I have tons of texts, but that's another topic. Finally, I removed the Spanish keyboard. I'm a happy Apple customer again. "
Hope it solves your problem too.
-
Oct 1, 2014 4:04 AM in response to mohanpby vincemomo,Hello,
I did have the same issue and couldn't make it work with IOS 8 (on an iPhone 5S)
after reinstalling the latest IOS 8.02 i still can't search the message (either sms or imessage).
Does anyone still have the same issue?
thx
-
Oct 1, 2014 8:19 PM in response to mohanpby Townsend Myers,I have an iPhone5. Joelrubi's fix worked for me.
-
Oct 2, 2014 10:45 AM in response to mohanpby ta2dqtpie,thank you!! that worked....was driving me bonkers!!
-
Oct 3, 2014 9:13 PM in response to mohanpby mink2,Changing the language and search method worked for me. Thx very much.
-
Oct 3, 2014 9:49 PM in response to Beavis38ghzby ta2dqtpie,Ok so only worked for one day!! Super frustrating!! Anyone else that changed the language does it still work for you?
-
Oct 4, 2014 1:44 AM in response to ta2dqtpieby corpski,Joelrubi's fix only works temporarily. I've had my 5s' message search fail again after a mere two hours or so. Absolutely frustrating and Apple is way too slow in fixing this major loss of functionality.
-
Oct 4, 2014 9:22 AM in response to corpskiby vincemomo,I Agree, I was wondering if there was any way to report this to apple beside calling the hotline...
I Heard that apple had a dedicated team listening to blogs and searching for any reported bugs...
hope they will find this one ...
-
Oct 15, 2014 11:52 PM in response to corpskiby mink2,The fix seems to be still working for me after many days.
-
Oct 17, 2014 6:56 PM in response to Beavis38ghzby Matt France,Why do we have to McGiver these crazy fixes? Apple should have the capacity to fix this in 2.2 seconds. This problem is seriously impacting my communications ability for my work and definitely influencing my decision to upgrade to an iPhone 6 or to a competitor instead. Dear Apple: please fix this TODAY.
-
Oct 21, 2014 1:49 AM in response to mohanpby mohanp,Seems like 8.1 fixes this problem...
iOS 8.0: searching old iMessages won't work. Using the "change language" workaround seemed to help.
iOS 8.0.2: doesn't work. And the "change language" workaround didn't work anymore....
iOS 8.1: searching old iMessages seems to be fixed. It's working on my iPhone 6 now.
Reminders:
Strongly suggest using iTunes to update to 8.1 (instead of doing it directly on your iPhone) - less problems encountered.
Don't forget to use iTunes to backup your iPhone before you do the iOS update.
Good luck!
-
Oct 6, 2016 9:45 PM in response to Beavis38ghzby trevor928,I have a 3 day old iphone 7 plus , I had this issue as well , i was running on a cloud backup from my old iphone 6 plus so what i did was backed up to the cloud on my new iphone 7 plus and then i reset and cleared out the 7 plus and then i downloaded the cloud backup of the 7 plus and somehow that fixed the issue!