-
All replies
-
Helpful answers
-
-
-
Aug 31, 2014 10:39 AM in response to sterling rby hockeyshark315,Thanks! just reset date and time and iMessage began to work.
-
Oct 4, 2014 2:44 PM in response to jem consultingby p41s3r,DUDE IM IN THE SAME POSITION! WHY CANT APPLE FIX THIS!!!!!!!!! AHHHHHHHHHH
-
-
Oct 4, 2014 3:41 PM in response to Ralph Johns (UK)by p41s3r,Here's a question for you Ralph, when I cleaned installed my OSX, why doesn't iMessage work?
-
Oct 5, 2014 12:13 PM in response to p41s3rby Ralph Johns (UK),Hi,
Because the issue does not lie with your Mac but the iMessages Servers and the current way Apple is insisting the device "registers" with the Server.
Unless you have this Error Message we can't prove that though
This can ONLY be fixed by contacting Apple Support.
That in itself can be fraught with difficulties as the Staff turn over is relatively high, leaving new people not knowing about pre-existing issues.
When you have checked everything else, Time Zone, Date and Time on computer and router, DNS settings, region and or country setting in the Messages app and on the computer and in the Contacts App, Serial Number, and then, if you don't get the pop up messages above you have all the symptoms but the pop up.
Logic says the outcome or fix is likely to be the same or closely related.
8:13 pm Sunday; October 5, 2014
iMac 2.5Ghz i5 2011 (Mavericks 10.9)
G4/1GhzDual MDD (Leopard 10.5.8)
MacBookPro 2Gb (Snow Leopard 10.6.8)
Mac OS X (10.6.8),
Couple of iPhones and an iPad -
Oct 30, 2014 2:32 AM in response to Ralph Johns (UK)by pascalfrommontpellier,If you're unable to login to FaceTime and iMessage because the login process repeatedly loops, check the time settings. If the time is not set to automatically adjust (Settings > General > Date & Time > Set Automatically > On), you might find that the login sequence for both FaceTime and iMessage loops. Once you set the time to adjust automatically, all is back to normal.
Enjoy
-
by Ralph Johns (UK),Oct 30, 2014 1:46 PM in response to pascalfrommontpellier
Ralph Johns (UK)
Oct 30, 2014 1:46 PM
in response to pascalfrommontpellier
Level 9 (72,994 points)
ApplicationsUmm,
Did you read this Thread ? (this is a link to a Post within this thread)
Re: Cannot login into iMessage
8:46 pm Thursday; October 30, 2014
iMac 2.5Ghz i5 2011 (Mavericks 10.9)
G4/1GhzDual MDD (Leopard 10.5.8)
MacBookPro 2Gb (Snow Leopard 10.6.8)
Mac OS X (10.6.8),
Couple of iPhones and an iPad -
Nov 11, 2014 2:31 AM in response to 3m3rg3ncyby Ali Beadle,Agreed - similar problem on an ipad after time zone change - turning "settings/general/date&time/set automatically" off and on again fixed it for me.
-
Jul 16, 2015 5:16 PM in response to AjaxOdessaby Travmau5,Same issue. Super frustrating. Was working fine. Then got the "could not sign into iMessage" error and it didn't work for a week. Just randomly started working today. I didn't do anything. Just started working. Now being flooded by notifications.
-
Jul 21, 2015 5:07 PM in response to AjaxOdessaby davidmxcanada,HALLELUJA!!!.... I FINALLY figured this out.
tl;dr: Make sure you set "Date & Time", as well as "Time Zone" automatically, NOT manually.
I've had this issue for months but I simply chose to ignore it due to more pressing matters. I sincerely thought that the only way I could get rid of the problem was to factory-reset my computer....
Luckily, it was actually another bug that tipped me off on what might have been the problem:
I was receiving emails on the "Mail" app on my Mac that would say "Tomorrow" instead of a normal received "time stamp".... it was obviously bizarre, but again, I'd ignored it due to lack of time, and the relative minor issue.
Running a small hostel in Cancun, Mexico, I received a booking confirmation via Booking.com that caused a lot of issues due to the fact that the email said "You have a booking for tonight", when in reality, the booking was for tomorrow. This piqued my interest enough to look into the date and time/time zone issue, and I realized that for some reason, my computer was set to the timezone of "Shanghai", and that I had (for some reason) changed the time manually to reflect the correct time on my Mac. This seemed to bug-out quite a few apps which seem to draw on this information.
The original reason for me playing with the time on my Mac was that Cancun legally changed timezones back in February, so there was a moment after the legislation passed that both Google AND Apple were giving people the wrong time. Clients were even checking in saying that no one (not even pilots on intercoms upon landing), were 100% sure what the local time it was.
When I set my time zone to "Cancun" just now, my computer still displayed the wrong time, but when I set the "Date & Time" setting to automatic, much to my surprise, it corrected itself!
This was the "aha!" moment I had for iMessages. I figured that maybe, I could never log-in because iMessages might be trying to sync different times at the same time, causing it to continue on an infinite error-loop, and thus, never log on.
As we all know, much to my relief, this was the issue, and while this really is a "first world problem", it was definitely REALLY annoying to not be able to share information via one platform/device.
So once again:
Click the apple at the top-left > System Preferences > Date & Time > Date & Time Tab > Check box "Set date and time automatically"
Then: > Time Zone Tab > Check Box "Set time zone automatically using current location"
- David
-
Aug 27, 2015 5:07 PM in response to sterling rby Bob Starman,I travelled from Canada to UK and IMessage stopped working with same sign in message. Changed time zone on return and removed the file mentioned in this thread. Opened IMessage again and it works.
-
Aug 27, 2015 5:13 PM in response to Ralph Johns (UK)by Bob Starman,This direction of removing the "bum" file solved my issue with logging into IMessage along with changing my time zone after recent travel and setting the time to automatically update.
-
Sep 7, 2015 11:09 AM in response to Bob Starmanby Steven Moore,I was having this problem and resetting the PRAM fixed it.
I have been using windows 7 in bootcamp to play windows games and find that using windows 7 in bootcamp seems to corrupt the PRAM occasionally.





