ZwiftMap for macOS

Things to be aware of

Security settings

Remember that you must adjust security settings as described in when you install the application.

Default security setting on macOSmacOS The operating system on the Mac computers from Apple complain that Zwiftmaps is from an unknown developer (the app isn’t signed with an Apple-recognized/trusted certificate). Requires going into System Preferences -> Security & Privacy -> click “Open Anyway”

Chat and ride/run data are disabled

Your user probably have insufficient access rights to enable capture of network traffic. You can enable it with the following command in Terminal (it will give your user read access to the network devices /dev/bpf*):

sudo chmod o+r /dev/bpf*

You must also activate Network capture features under Settings in ZwiftMap.

This should hopefully be enough to let ZwiftMap capture network traffic (from next time you start it and until the next reboot – see more below).

Crash when you start or exit ZwiftMap

If you get a crash window where you can choose to send an error report it is most likely because you have activated Network capture features under Settings in ZwiftMap but not changed the permissions for /dev/bpf* as described above. It is known to provoke program crashes.

Error in cap. open – probably insufficient access rights

This means that the permissions on the network devices /dev/bpf* are not set as described above.

You can set them with the chmod command shown but since the permissions do reset at every reboot you will have to do it after every reboot unless you automate it with a launch daemon job like this:

Do the following from Terminal:

sudo nano /Library/LaunchDaemons/com.zwifthacks.chmodbpf.plist

Simply paste the text below into the nano editor window:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "">
<plist version="1.0">
<string>/bin/chmod o+r /dev/bpf*</string>

Press ^O (ctrl+O) followed by Enter (to save the file).
Press ^X (ctrl+x) (to exit nano)

You have now created a launch daemon job which will change the permissions at every reboot.

To check that it changes the permissions correctly you can test run it with the following command in Terminal:

launchctl load /Library/LaunchDaemons/com.zwifthacks.chmodbpf.plist