Troubleshooting

Troubleshooting

Troubleshooting can be done in a series of ways. Below is a list of the current methods you can troubleshoot issues with the application.

Log File

• For a quick and easy solution, turn on verboseLogging under advanced in the preferences menu and check the main.log file for any errors or information that can help. You can find your log path here.

Auth Mode

• Authmode is just used for to help resolve login issues. All you need to do is enable the configuration option authMode or in the new UI, there's a checkbox for it. This should be disabled after login, it will cause issues if its enabled through normal application use.

Clean Installation

• A simple clean installation can be done by uninstalling the application (on Windows this can be done the System Setting) and clearing all application data:
• After you have uninstalled the application, you can begin by deleting the following folders if they exist:
• %APPDATA%\Apple Music
• %LOCALAPPDATA%\Programs\apple-music-electron
• %LOCALAPPDATA%\apple-music-electron-updater
• Then reinstall the application from here.

---

Troubleshooting Advanced

Enabling DevTools

• It is advised to turn on allowSetMenu variable in advanced section in config.json for troubleshooting. This will allow the Chrome DevTools like inspect element and access to the renderer console, this can all be done by doing CTRL + SHIFT + I.
• You can find all the documentation for the Chrome Dev Tools here.

JS Troubleshooting

• If you are creating a JavaScript file that you want to inject into the application, most errors will be moved into the renderer's console. JavaScript can also be run in the console if you'd like to test it first.
• It is also recommended that you try-catch all your code as this assists in narrowing down the cause of errors.

CSS Troubleshooting

• This is round about the same as it is for JS Troubleshooting. However, you cannot run CSS in the console (unless it is being done through a JS Function). CSS can be edited in Inspect Element and you can adjust global variables in the Inspect Element page, more information can be found in the DevTools documentation.

Common Issues

Authentication Issues (Error Message Item not available in your country / Apple Music is not available in your country or region)

*This can range from error messages like 'Apple Music is not available in your country or region.' or 'Item not available in your country'. Anything along those lines should be resolved if you follow the steps below.

2.5.0

• Follow the clean install guide above and make sure you do not have a VPN turned on.

2.4.0

• If you have done the previous and/or you are already on the v2.4.0 beta, then by simply turning on authMode in the settings menu which can be accessed by doing CTRL + Alt + S ( or ⌘ + ⌥ + S on a Mac) or through clicking on your profile picture and clicking App Settings. authMode should only be enabled for login in and should be disabled for the rest of the time. However, if it does run better for you with authMode, leave it on.

2.3.0 or lower

• Enabling (setting to true) disableCORS in the config.json file. This can be found in Documents/Apple Music if you are on Windows, config/'Apple Music' on Linux and Library/Application Support/Apple Music/ for MacOS.

• If this does not resolve your issue it is recommended to upgrade to the latest beta version which can be found here.

Configuration Missing Option (Error Message 'includes' of undefined)

• If you are experiencing errors that contain 'includes' of undefined or something along those lines, delete the preferences.json file found in the same directory of your log file then restart.