How to Fix Cannot sign into iMessage in secondary account on ESXi VMs
This mini-guide provides a structural approach to troubleshoot and fix the issue.
Prerequisites
- Confirm your hardware specifications (CPU, GPU, Motherboard).
- Ensure you have a bootable recovery USB and backup your EFI.
Fix Steps
- Review your system logs and verbose boot output for specific error codes.
- Ensure your OpenCore and kexts are up to date.
- Compare your configuration with the official Dortania guidelines.
Verification
- Reboot and verify if the functionality is restored and stable under typical usage.
Original Question:
I've got a VM I've been using for iMessage via Airmessage for awhile now. I attempted to add another account to the mac, with a brand new Apple ID so I could set this up for one of my kids.
iMessage says to call support and give them a customer code to allow the login. I have been trying to get that authenticated for some time, but have been escalated now and figured I'd try to stand up a fresh VM.
I followed this guide to generate proper values to use in the VMX file. Stood up a new VM on Mojave, and am getting the same "customer code" authentication failures within that VM for every account I try to authenticate.
It seems like requirements may have changed since I built my working VM but I can't seem to find any information out there about any values I might need to add to the VM, or how I can get authentication to work. The accounts works fine on a legit macbook air :/
Anyone know if there were recent changes and if there are any workarounds?
[link] [comments]
Post a Comment