Jump to content

Imessage and facetime Public Beta 2


  • Please log in to reply
108 replies to this topic

#1
Agostino9446

Agostino9446

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 415 posts
  • Gender:Male
  • Location:Aversa,CE

Hi guys this morning i updated yosemite from public beta 1 to 2..everything ok...but now i can't login imessage and facetime...both say that i have to call apple support,but before that i updated i was able to login...how can i do?ps.Appstore and icloud work



#2
sailor25462

sailor25462

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

I can copy this behaviour. Just updated from beta 1 to beta 2 and I'm now asked to contact customer support.

Appstore and itunes store working fine, though. (using clover 2818, trying update to 2830 now)

 

Edit: 2830 & r2795 don't change anything.



#3
Agostino9446

Agostino9446

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 415 posts
  • Gender:Male
  • Location:Aversa,CE

I can copy this behaviour. Just updated from beta 1 to beta 2 and I'm now asked to contact customer support.
Appstore and itunes store working fine, though. (using clover 2818, trying update to 2830 now)

Same like me...someone can help us?

#4
rvxtm

rvxtm

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 105 posts
  • Gender:Male
  • Location:Timisoara, Romania
  • Interests:Tech, Science, Biology, OSX86 stuff

same here as well



#5
Azzo94

Azzo94

    Uno che Dona..Si VEDE!

  • Donators
  • 359 posts
  • Gender:Male
  • Location:Firenze - Italy

Same here!



#6
Agostino9446

Agostino9446

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 415 posts
  • Gender:Male
  • Location:Aversa,CE
With dp6 is there same issue?

#7
frnic

frnic

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

Nope, Message woks for me on Beta 2. I have not tried Facetime



#8
sailor25462

sailor25462

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

Nope, Message woks for me on Beta 2. I have not tried Facetime

 

So, what did you do differently from us ?  :drool:

 

I tried 2818 (basically had it active when doing the update), so that's probably not doing the trick.



#9
arsradu

arsradu

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 279 posts
  • Gender:Male

Nope, Message woks for me on Beta 2. I have not tried Facetime

Are you sure you're using Public Beta 2 (build 14A329r) and not the DP2 aka Developer Preview 2 which was launched a while ago? Cause people tend to confuse the two of them. And I've got the exact same issue in Beta 2, and I also didn't have it in Beta 1. And no, it doesn't seem to have anything to do with Clover version.

Interestingly enough, it seems to happen with Mavericks as well (even after changing everything in Clover and resetting the Apple password) which means that the issue might not be software related, but server related.

Attached Files



#10
frnic

frnic

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

I need to retract that comment - it does appear that Messages and FaceTime are not working for me either. 

In addition I am seeing several programs with Icon buttons that the buttons do not work and they did work on the first beta. 

 

And yes, I am sure I am running the public beta version 2:
 

 System Version: OS X 10.10 (14A329r)

 Kernel Version: Darwin 14.0.0

 
Sorry about the confusion.


#11
Agostino9446

Agostino9446

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 415 posts
  • Gender:Male
  • Location:Aversa,CE
Ok...so everyone have this probelm..waiting for a solution...

#12
mcdougal33

mcdougal33

    InsanelyMac Protégé

  • Members
  • PipPip
  • 83 posts
  • Gender:Male

iMessage isn't working for me either on mavericks or yosemite beta 2.  I'm thinking apple is blocking non legit serials from using imessage/facetime now.  It wouldn't be hard for them to distinguish a legit serial from a non legit serial; after all they build the machines. I"m sure they have a list of every serial they've used.



#13
sbg

sbg

    InsanelyMac Protégé

  • Donators
  • 66 posts

Same problem for me with Public Beta 2 (14A329r) - was working fine with Public Beta 1 (and still works with Mavericks).



#14
HBP112358

HBP112358

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 171 posts
  • Location:USA

just got off the Phone with Apple Support. they changed the Auth Token again, (having a REAL MacBook Pro) telling them that I am having this problem makes it much easier to get resolved quickly, as they will talk with me.

 

once authenticated it will work until deauthenticated.

 

HBP



#15
sailor25462

sailor25462

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

just got off the Phone with Apple Support. they changed the Auth Token again, (having a REAL MacBook Pro) telling them that I am having this problem makes it much easier to get resolved quickly, as they will talk with me.
 
once authenticated it will work until deauthenticated.
 
HBP


I remember I may have seen a very short pop up of a message containing something like "token invalid" or so. Was too fast to read it properly.
My understanding is that with this new token, the use of this Apple ID will be impossible on whatever OS X installation, regardless of the real hardware behind? Can you confirm it was also deactivated on your mac book? It obviously has no impact on the iMessage usage on iPhone/iPad, etc.

So, what were the information support was asking? Anything that would require info from apple hardware?

I have seen some news about a massive increase of iMessage spam, due to the possibility of scripting iMessage under OS X. I just can't imagine apple will ask any Yosemite user to call support ones to authenticate properly by phone?

Maybe some new info they try to request from SMC, which is not available now?

#16
asapreta

asapreta

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 755 posts

Besides the number generated on the problem - customer code - (once I had the problem with my MacBook Pro) they ask for the product serial number.



#17
KibosJB

KibosJB

    InsanelyMac Protégé

  • Members
  • Pip
  • 28 posts

Having issues too, Messages still works on my iPad but refuses to work in Yosemite PB2 :(

 

iCloud won't sign in properly either, it signs me in and works but it is all greyed out and constantly asks to enter my password to continue using iCloud.

 

Is this the same issue or do I have other problems?



#18
sailor25462

sailor25462

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

Besides the number generated on the problem - customer code - (once I had the problem with my MacBook Pro) they ask for the product serial number.

 

I can confirm, calling customer support solves the issue.

As advised by many others, you will be asked for the serial, but being a good apple customer with one or more registered apple devices, you may want to have a good excuse for not having this at hand. They appreciate that their customers tend to be travelling a lot and have no access to the device at the time of calling  :blush: Instead give them your apple id and kindly ask them to register the iMessage/facetime code. They're nice and friendly people!

 

The still unsolved question is, why this happened just after updating to public beta 2.... :angry:

 

Nothing else had been changed.

 

Btw.: I added the still missing SMUUID in Clover configurator (SMBIOS), as well as a custom UUID (in system parameters, generated via terminal command uuidgen), although imessage_debug did show good info (no garbage, i.e. zero values).

This did a reset on my keychain/icloud and I was asked to auth again via another registered apple product.  

This also gave me a new code in iMessage to pass to customer care!

I didn't change my serial no., though.

 

As for the SMUUID, last part matches my MAC address (just in case, yes I know some say it's not necessary), custom UUID is totally different from the SMUUID.

I remember there were some discussions about those, but frankly speaking, for me it's not totally clear how they correlate (or not).

I'm afraid I'm not into this topic deeply enough  :unsure:

 

But from an academical standpoint I'm still interested to learn, so if we can sort this miracle out in some way  :angel_not:


Having issues too, Messages still works on my iPad but refuses to work in Yosemite PB2 :(

 

iCloud won't sign in properly either, it signs me in and works but it is all greyed out and constantly asks to enter my password to continue using iCloud.

 

Is this the same issue or do I have other problems?

 

I think you may have more issues than we do (did  :angel: )

 

I could properly sign into App Store, iCloud, itunes and such. It was only affecting iMessage and FaceTime.

 

You may want to check with the comprehensive how-to's available. They're pages long, so please forgive me if I'm not repeating it here.



#19
Agostino9446

Agostino9446

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 415 posts
  • Gender:Male
  • Location:Aversa,CE

I can confirm, calling customer support solves the issue.
As advised by many others, you will be asked for the serial, but being a good apple customer with one or more registered apple devices, you may want to have a good excuse for not having this at hand. They appreciate that their customers tend to be travelling a lot and have no access to the device at the time of calling :blush: Instead give them your apple id and kindly ask them to register the iMessage/facetime code. They're nice and friendly people!

The still unsolved question is, why this happened just after updating to public beta 2.... :angry:

Nothing else had been changed.

Btw.: I added the still missing SMUUID in Clover configurator (SMBIOS), as well as a custom UUID (in system parameters, generated via terminal command uuidgen), although imessage_debug did show good info (no garbage, i.e. zero values).
This did a reset on my keychain/icloud and I was asked to auth again via another registered apple product.
This also gave me a new code in iMessage to pass to customer care!
I didn't change my serial no., though.

As for the SMUUID, last part matches my MAC address (just in case, yes I know some say it's not necessary), custom UUID is totally different from the SMUUID.
I remember there were some discussions about those, but frankly speaking, for me it's not totally clear how they correlate (or not).
I'm afraid I'm not into this topic deeply enough :unsure:

But from an academical standpoint I'm still interested to learn, so if we can sort this miracle out in some way :angel_not:


I think you may have more issues than we do (did :angel: )

I could properly sign into App Store, iCloud, itunes and such. It was only affecting iMessage and FaceTime.

You may want to check with the comprehensive how-to's available. They're pages long, so please forgive me if I'm not repeating it here.

So you solved the issues calling customers support?



#20
sailor25462

sailor25462

    InsanelyMac Protégé

  • Members
  • Pip
  • 26 posts

So you solved the issues calling customers support?

 

YES !!!

 

If calling center system asks you to give your serial number, just keep typing "0", it will finally let you through to their staff.


Edited by sailor25462, 23 August 2014 - 12:30 PM.






1 user(s) are reading this topic

1 members, 0 guests, 0 anonymous users


© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy