Helder Monteiro

Q: Facetime for Mac 1.0.4

I have a macmini running MacOS 10.6.8 and recently purchased in Apple Store the new FaceTime. Installed it and I can't activate it with my Apple ID. Any thoughts??

Posted on Apr 12, 2014 6:15 PM

Close

Q: Facetime for Mac 1.0.4

  • All replies
  • Helpful answers

first Previous Page 4 of 4
  • by Corgi Momo,

    Corgi Momo Corgi Momo Apr 17, 2014 4:44 PM in response to Helder Monteiro
    Level 1 (0 points)
    Apr 17, 2014 4:44 PM in response to Helder Monteiro

    MacRumors reports that many of the iOS6 users and OSX 10.8 users are currently experiencing FaceTime connection trouble.

     

    http://www.macrumors.com/2014/04/17/ios-6-facetime-issues/

     

    While the patterns of the trouble appear different (i.e. not connecting v.s. not siging-in), it may suggest that our v.1.0.4 trouble might be also related to the entire FaceTime system glitch, rather than a bug in the application itself.

     

    Let's watch.

  • by MarinT,

    MarinT MarinT Apr 18, 2014 7:39 AM in response to Corgi Momo
    Level 1 (0 points)
    Apr 18, 2014 7:39 AM in response to Corgi Momo

    Guys, just to give you an update, I tried to move back to version 1.0.2, which was working fine, but now ran into issues with "registering device does not have appropriate credentials", seems I'm completely stuck now, can't buy (for the 2nd time) Facetime from the App store either as it says it is already installed.

     

    The solution: I installed Microsoft Skype. Works like a charm. Will use it until Apple releases a new version of FaceTime. It's a shame, I hope they don't screw up with their new product launch this year, otherwise I should definately start selling my Apple shares .....

  • by MacLion,

    MacLion MacLion Apr 20, 2014 10:32 PM in response to Corgi Momo
    Level 2 (205 points)
    Apr 20, 2014 10:32 PM in response to Corgi Momo

    For an iMac running Snow Leopard 10.6.8, I applied the update as well and didn't use FaceTime right away - AND now I just tried FaceTime and found this! Very disappointing! It seems lately no updates are safe anymore!

     

    Also if you don't have a back up of the right time period no way to revert back to 1.0.2.

     

    There seems to have been a rash of troublesome updates recently; from the late 2008 macbook pro loss of wifi with 10.8.5, the recent Adobe Flash 13.0.0.182 update and now this! It gets frustrating for end users who get used to things just working! The one thing Adobe did was give some transparency on the issue and the effort to fix it; and had a fix out within a week.

     

    I hope Apple is getting a fix in the works soon!

  • by Corgi Momo,

    Corgi Momo Corgi Momo Apr 22, 2014 10:42 PM in response to Helder Monteiro
    Level 1 (0 points)
    Apr 22, 2014 10:42 PM in response to Helder Monteiro

    FaceTime 1.0.5 update for OSX 10.6 was released at App Store.

    Hopefully it may resolve the sign-in trouble caused by 1.0.4 update.

     

    http://www.macrumors.com/2014/04/23/facetime-fix-older-versions-osx/

  • by MacLion,

    MacLion MacLion Apr 22, 2014 11:15 PM in response to Corgi Momo
    Level 2 (205 points)
    Apr 22, 2014 11:15 PM in response to Corgi Momo

    Just saw that! Downloading now, hopefully it does the job!

  • by MacLion,Solvedanswer

    MacLion MacLion Apr 22, 2014 11:21 PM in response to MacLion
    Level 2 (205 points)
    Apr 22, 2014 11:21 PM in response to MacLion

    Seems to work well on the Mac now, but still seems to be unrepaired for connecting to devices running iOS 6. Hoping there's a fix for that as not all can go to iOS 7 as a fix.

  • by Helder Monteiro,

    Helder Monteiro Helder Monteiro Apr 23, 2014 5:03 PM in response to Helder Monteiro
    Level 1 (15 points)
    Apr 23, 2014 5:03 PM in response to Helder Monteiro

    To  all that were affected by FaceTime 1.0.4:

    Apple released an update, FaceTime 1.0.5, last Tuesday. I downloaded it and it's functioning well. So, after all, our complains got (perhaps!..) our goals! To all of you, my best regards, my thanks and greetings from Aveiro, Portugal

  • by Helder Monteiro,

    Helder Monteiro Helder Monteiro Apr 23, 2014 5:06 PM in response to Corgi Momo
    Level 1 (15 points)
    Apr 23, 2014 5:06 PM in response to Corgi Momo

    So long Corgi!! You're special, my first reply! A special thanks to Japan from Aveiro, Portugal!

    Bye

  • by Corgi Momo,

    Corgi Momo Corgi Momo Apr 23, 2014 5:40 PM in response to Helder Monteiro
    Level 1 (0 points)
    Apr 23, 2014 5:40 PM in response to Helder Monteiro

    I thank YOU, Helder.

     

    I came here to see if there is some useful information on my v.1.0.4 trouble, as I could not find any in Japan. Thanks to you, I got the confidence that the trouble is not happening only in my environment, but there is something wrong with the update itself.

     

    As my father-in-law is now in a hospital, I have not applied the v.1.0.5 update to his MacBook yet. I will do so today, and I hope it will work well.

     

    Thank you again.

  • by MacLion,

    MacLion MacLion Apr 24, 2014 12:30 PM in response to MacLion
    Level 2 (205 points)
    Apr 24, 2014 12:30 PM in response to MacLion

    The official response:

     

    http://support.apple.com/kb/TS5419

     

    Going to 6.1.6 on iDevices should solve the issue with iOS 6.

  • by jkcymbal,

    jkcymbal jkcymbal Apr 25, 2014 10:08 AM in response to Corgi Momo
    Level 1 (0 points)
    Apr 25, 2014 10:08 AM in response to Corgi Momo

    Just updated from the non working 1.0.4 to 1.0.5 and still it doesn't work...

     

    very disapointed/frustated with all this... it was perfect for me on 1.0.2

  • by broadway al,

    broadway al broadway al May 24, 2014 6:25 PM in response to MacLion
    Level 1 (0 points)
    May 24, 2014 6:25 PM in response to MacLion

    It's been a while because after going through the updates I seemed to have had the sound disapperance issue resolved. Well guess what? It went back to the same old issue only this time it took a longer time.

    I really hoped that this was something Apple had finally taken care of but it looks as though they tried the windows system of not looking for the bad code but just rewriting a newer version and hope the cause was lost.

first Previous Page 4 of 4