This man is a genius lolHah, so I was right about the cause. They added ArchiveDecryptionKey to the affected devices now and it's fixed.
Good job!Hah, so I was right about the cause. They added ArchiveDecryptionKey to the affected devices now and it's fixed.
This standard policy, they can't troubleshoot with a beta on your device.when I had an issue with my Mac, they cut me off and told me they won't help me unless I install the latest public released OS
Or just wait until Apple fix itHi,
Unpair AWU 2, pair again using one backup and you will be able to install the update.
Or they just stop responding after you’ve sent all the information they requested - probably because they have no idea why it’s doing what it’s doing.This would be too funny if it wasn't so sad and true. This is exactly my experience with Apple support, beta reports and dealing with their engineers. I keep finding edge cases, report, report, wait, wait, then finally raise such a fuss that they finally collect more information, confirm I was right all along and push a semi-fix out in an upcoming release (think USB drives sleeping and ejecting, universal control, etc...) The universal control one took me years to get their attention on.
It is A BETA. Do you know what a beta is ? No support granted for a beta. Use it at your own risk.Not worry everyone, for Apple Support is here to the rescue. Here is the standard response:
1. This is not an issue because if it was, Apple Support would know about it before a customer does, because they talk to millions of customers an hour.
2. For issues like this, you'll need to re-install WatchOS and set-up the watch as new. If the issue persists, you'll need to install a profile and collect logs, with Mail logging enabled, just to be safe. After you collect the logs, you'll upload them to Apple to attach to the RTA.
3. Engineering will reply in 48 hr, confirming this is a known issue, there is no current fix, keep your device up to date, and no further troubleshooting will be provided.