Apple's failure on the up to date codes may have a benefit. Support forums are filling with some scary sounding bugs for Mountain Lion. When Apple finally decides to allow updates to go forward, they might include more bug fixes.
Well got mine now and working correctly, just so others do know. Seems they are back on track.
It appears those who got the bad codes are the only ones getting new ones. Those of us who haven't gotten any e-mails haven't gotten a code yet. I don't feel like waiting until next Tuesday to get Mountain Lion when I don't have to.
I went ahead and just bought it and e-mailed customer service for a refund. I assume they will refund it. If they don't, I'll just move up the chain until they do. I'll report back.
It appears those who got the bad codes are the only ones getting new ones. Those of us who haven't gotten any e-mails haven't gotten a code yet. I don't feel like waiting until next Tuesday to get Mountain Lion when I don't have to.
I went ahead and just bought it and e-mailed customer service for a refund. I assume they will refund it. If they don't, I'll just move up the chain until they do. I'll report back.
What a cruel joke. Purchased it at 12:37pm, at 1:08pm I get the code.
You act as if there is no causality there Now you get to chase down a customer service issue for a potential $20 payoff. Oh the joy.
Causality? You think Apple is waiting for customers to pay $20 for ML so they can then issue the redeem code? That has to be the worse conspiracy against Apple I've ever heard.
Causality? You think Apple is waiting for customers to pay $20 for ML so they can then issue the redeem code? That has to be the worse conspiracy against Apple I've ever heard.
I think he means the "casualty" is that even if I didn't get a code- I still have to get CS to reimburse the $20- which might be a challenge. I don't think it will be though. I know I'm not a huge company or anything- but I have 18 Apple products registered... that should hold some weight. ;-)
As someone else already mentioned: this is something databases were designed to handle.
But to offer a simple solution to this example:
user1 hits instance1. instance1 requests a lock on code1, obtains the lock, and issues code1 to user1. instance1 ensures the database is updated before the lock on code1 is released.
user2 hits instance2. instance2 requests a lock on code1, isn't able to obtain the lock because instance1 already holds it, and moves on to code2.
Uhmm, should the codes be generated uuid's? Then the duplicated codes problem would never happen. That's -1 for whoever was working on the system. If SJ was still there, this would never happen. (Thinking... anything like this happened before?...) Miss SJ...
As someone else already mentioned: this is something databases were designed to handle.
But to offer a simple solution to this example:
user1 hits instance1. instance1 requests a lock on code1, obtains the lock, and issues code1 to user1. instance1 ensures the database is updated before the lock on code1 is released.
user2 hits instance2. instance2 requests a lock on code1, isn't able to obtain the lock because instance1 already holds it, and moves on to code2.
Uhmm, should the codes be generated uuid's? Then the duplicated codes problem would never happen. That's -1 for whoever was working on the system. If SJ was still there, this would never happen. (Thinking... anything like this happened before?...)
Well, after waiting for 3 1/2 days with no reply, I decided to try registering my device for the third time. The first two times I got a confirmation code but no email. This time it took about 3 seconds to get my confirmation email. So, it looks like Apple just plain lost the original registrations. If you haven't gotten an email yet you probably just need to do the up to date application again.
Comments
Originally Posted by Andysol
As if he meant actually downloading it from the App store and not up-to-date (which is what this thread is).
Thanks for missing the point entirely.
Apple's failure on the up to date codes may have a benefit. Support forums are filling with some scary sounding bugs for Mountain Lion. When Apple finally decides to allow updates to go forward, they might include more bug fixes.
Quote:
Originally Posted by Tallest Skil
Thanks for missing the point entirely.
I'd love to hear the point I missed.
Well got mine now and working correctly, just so others do know. Seems they are back on track.
Quote:
Originally Posted by Rokrad
Well got mine now and working correctly, just so others do know. Seems they are back on track.
It appears those who got the bad codes are the only ones getting new ones. Those of us who haven't gotten any e-mails haven't gotten a code yet. I don't feel like waiting until next Tuesday to get Mountain Lion when I don't have to.
I went ahead and just bought it and e-mailed customer service for a refund. I assume they will refund it. If they don't, I'll just move up the chain until they do. I'll report back.
Quote:
Originally Posted by Andysol
It appears those who got the bad codes are the only ones getting new ones. Those of us who haven't gotten any e-mails haven't gotten a code yet. I don't feel like waiting until next Tuesday to get Mountain Lion when I don't have to.
I went ahead and just bought it and e-mailed customer service for a refund. I assume they will refund it. If they don't, I'll just move up the chain until they do. I'll report back.
What a cruel joke. Purchased it at 12:37pm, at 1:08pm I get the code.
Contact MAS support and tell them you want a refund and why.
Just received my two emails from Apple. 48 hours from registering. Downloading Mountain Lion now. Glad i held off from purchasing the update.
All is good.
You act as if there is no causality there
Causality? You think Apple is waiting for customers to pay $20 for ML so they can then issue the redeem code? That has to be the worse conspiracy against Apple I've ever heard.
Quote:
Originally Posted by SolipsismX
Causality? You think Apple is waiting for customers to pay $20 for ML so they can then issue the redeem code? That has to be the worse conspiracy against Apple I've ever heard.
I think he means the "casualty" is that even if I didn't get a code- I still have to get CS to reimburse the $20- which might be a challenge. I don't think it will be though. I know I'm not a huge company or anything- but I have 18 Apple products registered... that should hold some weight. ;-)
Quote:
Originally Posted by auxio
As someone else already mentioned: this is something databases were designed to handle.
But to offer a simple solution to this example:
user1 hits instance1. instance1 requests a lock on code1, obtains the lock, and issues code1 to user1. instance1 ensures the database is updated before the lock on code1 is released.
user2 hits instance2. instance2 requests a lock on code1, isn't able to obtain the lock because instance1 already holds it, and moves on to code2.
Uhmm, should the codes be generated uuid's? Then the duplicated codes problem would never happen. That's -1 for whoever was working on the system. If SJ was still there, this would never happen. (Thinking... anything like this happened before?...) Miss SJ...
Quote:
Originally Posted by auxio
As someone else already mentioned: this is something databases were designed to handle.
But to offer a simple solution to this example:
user1 hits instance1. instance1 requests a lock on code1, obtains the lock, and issues code1 to user1. instance1 ensures the database is updated before the lock on code1 is released.
user2 hits instance2. instance2 requests a lock on code1, isn't able to obtain the lock because instance1 already holds it, and moves on to code2.
Uhmm, should the codes be generated uuid's? Then the duplicated codes problem would never happen. That's -1 for whoever was working on the system. If SJ was still there, this would never happen. (Thinking... anything like this happened before?...)
Originally Posted by ipen
If SJ was still there, this would never happen. (Thinking... anything like this happened before?...)
Stop that. You know for a fact it's a blatant lie.
Finally got mine after around 36 hours, all is fine now!
Well, after waiting for 3 1/2 days with no reply, I decided to try registering my device for the third time. The first two times I got a confirmation code but no email. This time it took about 3 seconds to get my confirmation email. So, it looks like Apple just plain lost the original registrations. If you haven't gotten an email yet you probably just need to do the up to date application again.