starred/Docker-OSX
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-01-11 21:10:25 +01:00
Code Issues 411 Packages Projects Releases Wiki Activity

Anyone having success with iMessage? #390

New Issue
Open
opened 2025-12-29 00:26:04 +01:00 by adam · 8 comments
adam commented 2025-12-29 00:26:04 +01:00
Owner
Copy Link

Originally created by @HansDaigle on GitHub (Aug 3, 2022).

I'm having no success with iMessage.

  • I tried with a fresh account
  • I tried with an account tied to a physical iPhone that was created in 2020

I followed the instructions here: https://github.com/sickcodes/Docker-OSX/issues?q=156

Both accounts were blocked when I tried to log in to iMessage.

This is the command I run:

docker run -it \
    --device /dev/kvm \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -p 50922:10022 \
    -e GENERATE_SPECIFIC=true \
    -e DEVICE_MODEL="${DEVICE_MODEL}" \
    -e SERIAL="${SERIAL}" \
    -e BOARD_SERIAL="${BOARD_SERIAL}" \
    -e UUID="${UUID}" \
    -e MAC_ADDRESS="${MAC_ADDRESS}" \
    -v "${PWD}/existing_disk.img:/image" \
    sickcodes/docker-osx:naked

I tried with a BigSur image and a Monterey image, I also tried at least 3 different sets of unique machine numbers.

./custom/generate-unique-machine-values.sh \
        --count 1 \
        --tsv ~/my_permanent_serial_number.tsv \
        --output-env ~/my_permanent_serial_number.sh

+++

My question is: Is anyone having success with iMessage? If so how are you generating the unique machine numbers?

Originally created by @HansDaigle on GitHub (Aug 3, 2022). I'm having no success with iMessage. - I tried with a fresh account - I tried with an account tied to a physical iPhone that was created in 2020 I followed the instructions here: https://github.com/sickcodes/Docker-OSX/issues?q=156 Both accounts were blocked when I tried to log in to iMessage. - The fresh account was fully blocked getting the "You cannot sign in iMessage on this mac at this time" error. - The second account is in a login logout loop with no errors. Apparently, the solution is to call apple: https://www.reddit.com/r/MacOS/comments/l1wg1l/imessage_on_macos_keeps_logging_me_out/. This is the command I run: ``` docker run -it \ --device /dev/kvm \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -p 50922:10022 \ -e GENERATE_SPECIFIC=true \ -e DEVICE_MODEL="${DEVICE_MODEL}" \ -e SERIAL="${SERIAL}" \ -e BOARD_SERIAL="${BOARD_SERIAL}" \ -e UUID="${UUID}" \ -e MAC_ADDRESS="${MAC_ADDRESS}" \ -v "${PWD}/existing_disk.img:/image" \ sickcodes/docker-osx:naked ``` I tried with a BigSur image and a Monterey image, I also tried at least 3 different sets of unique machine numbers. ``` ./custom/generate-unique-machine-values.sh \ --count 1 \ --tsv ~/my_permanent_serial_number.tsv \ --output-env ~/my_permanent_serial_number.sh ``` +++ My question is: **Is anyone having success with iMessage? If so how are you generating the unique machine numbers?**
adam commented 2025-12-29 00:26:06 +01:00
Author
Owner
Copy Link

@rahmnathan commented on GitHub (Aug 17, 2022):

I'm facing the same issue.

@rahmnathan commented on GitHub (Aug 17, 2022): I'm facing the same issue.
adam commented 2025-12-29 00:26:06 +01:00
Author
Owner
Copy Link

@ju-li commented on GitHub (Sep 27, 2022):

You have to call Apple Support and give them the customer code in the error message. They'll activate it for the machine number that generated the customer code. Blue Bubbles has a good explanation of it in section "Error Messages": https://docs.bluebubbles.app/server/advanced/macos-virtualization/running-a-macos-vm/enabling-imessage-in-a-vm

@ju-li commented on GitHub (Sep 27, 2022): You have to call Apple Support and give them the customer code in the error message. They'll activate it for the machine number that generated the customer code. Blue Bubbles has a good explanation of it in section "Error Messages": https://docs.bluebubbles.app/server/advanced/macos-virtualization/running-a-macos-vm/enabling-imessage-in-a-vm
adam commented 2025-12-29 00:26:07 +01:00
Author
Owner
Copy Link

@acheong08 commented on GitHub (Sep 28, 2022):

Same issue but I am not getting an error message. It just logs me out once I successfully log in

@acheong08 commented on GitHub (Sep 28, 2022): Same issue but I am not getting an error message. It just logs me out once I successfully log in
adam commented 2025-12-29 00:26:07 +01:00
Author
Owner
Copy Link

@ju-li commented on GitHub (Sep 28, 2022):

Same issue but I am not getting an error message. It just logs me out once I successfully log in

I had that issue and kept trying to login and the error message showed up 🤷

@ju-li commented on GitHub (Sep 28, 2022): > Same issue but I am not getting an error message. It just logs me out once I successfully log in I had that issue and kept trying to login and the error message showed up 🤷
adam commented 2025-12-29 00:26:08 +01:00
Author
Owner
Copy Link

@arty01238 commented on GitHub (Apr 12, 2023):

Was this ever resolved?

@arty01238 commented on GitHub (Apr 12, 2023): Was this ever resolved?
adam commented 2025-12-29 00:26:08 +01:00
Author
Owner
Copy Link

@ju-li commented on GitHub (Apr 12, 2023):

Was this ever resolved?

@arty01238 just do what's laid out in Error Messages: https://docs.bluebubbles.app/server/advanced/macos-virtualization/running-a-macos-vm/enabling-imessage-in-a-vm

@ju-li commented on GitHub (Apr 12, 2023): > Was this ever resolved? @arty01238 just do what's laid out in Error Messages: https://docs.bluebubbles.app/server/advanced/macos-virtualization/running-a-macos-vm/enabling-imessage-in-a-vm
adam commented 2025-12-29 00:26:08 +01:00
Author
Owner
Copy Link

@Rossbro2 commented on GitHub (Jul 21, 2024):

Was there an update made on Apple's side that blocks iMessage for Docker-OSX? This was working for me about a year ago, then all the sudden I can't sign into iMessage anymore, despite logging into the OS and iCloud with my Apple ID. Sign into iMessage, and after a couple seconds, it goes directly back to the iMessage login screen. No "customer code" prompt/window shows 🤷🏼‍♂️

I thought there was something messed up on my system but I did an entirely new fresh install with the same problem. Called Apple support and they directed me to updating to the latest Mac OS, but that fails also. I can see the iMac Pro as a "device" on my iPad, but it doesn't show up on the Apple support website. What gives?

docker run -it \
    --device /dev/kvm \
    -p 50922:10022 \
    -p 5999:5999 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e GENERATE_UNIQUE=true \
    -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \
    --name MacOS \
    sickcodes/docker-osx:ventura

I verified SERIAL, BOARD_SERIAL, and UUID are all non-blank and appear legit. However, MAC_ADDRESS doesn't seem right (:##:##:##), and ROM is blank... Am I doing something wrong? I assumed GENERATE_UNIQUE=true would've taken care of things.

Thanks in advance!

@sickcodes 👀

@Rossbro2 commented on GitHub (Jul 21, 2024): Was there an update made on Apple's side that blocks iMessage for Docker-OSX? This was working for me about a year ago, then all the sudden I can't sign into iMessage anymore, despite logging into the OS and iCloud with my Apple ID. Sign into iMessage, and after a couple seconds, it goes directly back to the iMessage login screen. No "customer code" prompt/window shows 🤷🏼‍♂️ I thought there was something messed up on my system but I did an entirely new fresh install with the same problem. Called Apple support and they directed me to updating to the latest Mac OS, but that fails also. I can see the iMac Pro as a "device" on my iPad, but it doesn't show up on the Apple support website. What gives? ``` docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -p 5999:5999 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e GENERATE_UNIQUE=true \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \ --name MacOS \ sickcodes/docker-osx:ventura ``` I verified `SERIAL`, `BOARD_SERIAL`, and `UUID` are all non-blank and appear legit. However, `MAC_ADDRESS` doesn't seem right (`:##:##:##`), and `ROM` is blank... Am I doing something wrong? I assumed `GENERATE_UNIQUE=true` would've taken care of things. Thanks in advance! @sickcodes 👀
adam commented 2025-12-29 00:26:09 +01:00
Author
Owner
Copy Link

@ju-li commented on GitHub (Jul 23, 2024):

Was there an update made on Apple's side that blocks iMessage for Docker-OSX? This was working for me about a year ago, then all the sudden I can't sign into iMessage anymore, despite logging into the OS and iCloud with my Apple ID. Sign into iMessage, and after a couple seconds, it goes directly back to the iMessage login screen. No "customer code" prompt/window shows 🤷🏼‍♂️

I thought there was something messed up on my system but I did an entirely new fresh install with the same problem. Called Apple support and they directed me to updating to the latest Mac OS, but that fails also. I can see the iMac Pro as a "device" on my iPad, but it doesn't show up on the Apple support website. What gives?

docker run -it \
    --device /dev/kvm \
    -p 50922:10022 \
    -p 5999:5999 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e GENERATE_UNIQUE=true \
    -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \
    --name MacOS \
    sickcodes/docker-osx:ventura

I verified SERIAL, BOARD_SERIAL, and UUID are all non-blank and appear legit. However, MAC_ADDRESS doesn't seem right (:##:##:##), and ROM is blank... Am I doing something wrong? I assumed GENERATE_UNIQUE=true would've taken care of things.

Thanks in advance!

@sickcodes 👀

GENERATE_UNIQUE=true doesn't guarantee that the generated SERIAL, etc are valid. It was working for you before but you didn't persist the valid value across reboots using GENERATE_SPECIFIC=true
So when you rebooted, you lost your previously valid serial numbers
See: https://github.com/sickcodes/Docker-OSX?tab=readme-ov-file#making-serial-numbers-persist-across-reboots

I think it's best to follow this method for generating serials and then testing them: https://dortania.github.io/OpenCore-Post-Install/universal/iservices.html#generate-an-uuid
And then telling the container to use the specific serials that you've tested

@ju-li commented on GitHub (Jul 23, 2024): > Was there an update made on Apple's side that blocks iMessage for Docker-OSX? This was working for me about a year ago, then all the sudden I can't sign into iMessage anymore, despite logging into the OS and iCloud with my Apple ID. Sign into iMessage, and after a couple seconds, it goes directly back to the iMessage login screen. No "customer code" prompt/window shows 🤷🏼‍♂️ > > I thought there was something messed up on my system but I did an entirely new fresh install with the same problem. Called Apple support and they directed me to updating to the latest Mac OS, but that fails also. I can see the iMac Pro as a "device" on my iPad, but it doesn't show up on the Apple support website. What gives? > > ``` > docker run -it \ > --device /dev/kvm \ > -p 50922:10022 \ > -p 5999:5999 \ > -v /tmp/.X11-unix:/tmp/.X11-unix \ > -e GENERATE_UNIQUE=true \ > -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ > -e "DISPLAY=${DISPLAY:-:0.0}" \ > -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \ > --name MacOS \ > sickcodes/docker-osx:ventura > ``` > > I verified `SERIAL`, `BOARD_SERIAL`, and `UUID` are all non-blank and appear legit. However, `MAC_ADDRESS` doesn't seem right (`:##:##:##`), and `ROM` is blank... Am I doing something wrong? I assumed `GENERATE_UNIQUE=true` would've taken care of things. > > Thanks in advance! > > @sickcodes 👀 `GENERATE_UNIQUE=true` doesn't guarantee that the generated `SERIAL`, etc are valid. It was working for you before but you didn't persist the valid value across reboots using `GENERATE_SPECIFIC=true` So when you rebooted, you lost your previously valid serial numbers See: https://github.com/sickcodes/Docker-OSX?tab=readme-ov-file#making-serial-numbers-persist-across-reboots I think it's best to follow this method for generating serials and then testing them: https://dortania.github.io/OpenCore-Post-Install/universal/iservices.html#generate-an-uuid And then telling the container to use the specific serials that you've tested
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX#390
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?