MuseScore icon indicating copy to clipboard operation
MuseScore copied to clipboard

[MU4 Issue] Muse Hub doesn't launch on macOS: "Unable to connect to helper, please contact support."

Open D-Tylr opened this issue 2 years ago • 11 comments

Describe the bug Installed the new muse hub app today, but something strange is happening. I get an error saying "unable to connect to helper, please contact support." Every time I try to open muse hub it tries to install the helper but fails.

I have stable internet I read something that said to "right click the hub logo and select reinstall helper" but that option doesn't exist. Sometimes I can get muse hub to open, but nothing loads and I think it's more of a glitch than properly opening up

To Reproduce Steps to reproduce the behavior:

  1. Download Muse Hub on mac system
  2. Move Muse Hub to application folder as per installer
  3. Open Muse Hub
  4. Error as described above: "unable to connect to helper, please contact support."

Expected behavior The program should download whatever the helper program is and operate normally.

Platform information

  • OS: MacOS 12.5.1

D-Tylr avatar Dec 14 '22 18:12 D-Tylr

Is it the first time you're installing Muse Hub, or did you already have it installed previously?

Does the error say anything more than "unable to connect to helper, please contact support."?

cbjeukendrup avatar Dec 14 '22 18:12 cbjeukendrup

Screen Shot 2022-12-14 at 2 03 46 PM

edit: apologies, this is my first time downloading music hub. never had a development version.

D-Tylr avatar Dec 14 '22 19:12 D-Tylr

I have the same issue as described above. On Ventura 13.0.1

BTW, it seems weird reporting bugs in non-open-source software (MuseHub) on the repository for open source software (MuseScore).

gary-schiltz avatar Dec 14 '22 19:12 gary-schiltz

Screen Shot 2022-12-14 at 2 03 46 PM

In fact, I'm having this too, after updating to 0.9.12 (and seemingly successfully using it for a while after installing the update).

When I tried to launch MuseHub at some point, I was prompted for my password to install the helper (even though I had already successfully used the Hub after installing 0.9.12), and then it gave this time-out error message.

I tried a few times, and sometimes the Hub did launch (without asking for password), but it wouldn't load any content.

Then I clicked the "uninstall" button in the Hub, hoping that uninstalling and re-installing would fix it, and redownloaded it from musehub.com, but now I only get the time-out error.

It also looks like some people have reported the same on Discord: https://discord.com/channels/818804595450445834/818804595450445837/1052656422070013992

cbjeukendrup avatar Dec 14 '22 19:12 cbjeukendrup

Huh... Just tried it again, and now it launched one time without asking for password, loading only the logos of the four apps, but not the rest. Then quit and tried yet another time, and this time I did get a password prompt, and after that it also launched successfully and even seems to have loaded all content. Then tried a third time and now it asks for password again and gives timeout... so it looks like it's doing something different on every launch! Here are some logs, in case it helps: Muse Hub logs 14 dec.zip

cbjeukendrup avatar Dec 14 '22 19:12 cbjeukendrup

I have the same issue as described above. On Ventura 13.0.1

BTW, it seems weird reporting bugs in non-open-source software (MuseHub) on the repository for open source software (MuseScore).

Definitely agreed! In the Muse Hub application, you can click on the "contact support" icon; of course with installation issues this is not available :/

In the meantime, feel free to report at https://musehub.zendesk.com -- here we have a support forum set up as well as resolutions for some common issues.

Thanks for the logs; I'm looking into the cause of this now.

iamtesch avatar Dec 14 '22 21:12 iamtesch

I had the same response, just after I had set a different download location in settings. I had to remove the com.muse.hub directory to make the app run again. sudo rm -r ~/Library/Containers/com.muse.hub Have in mind that after this command, all settings are deleted. So, please use with caution.

kolydart avatar Dec 17 '22 15:12 kolydart

I had the same response, just after I had set a different download location in settings. I had to remove the com.muse.hub directory to make the app run again. sudo rm -r ~/Library/Containers/com.muse.hub Have in mind that after this command, all settings are deleted. So, please use with caution.

Same here... Even if I try to download the library in an external drive, the download stays at 1% forever.

Is it possible to be related to external drive access maybe?

oporapunk avatar Dec 21 '22 18:12 oporapunk

The issue was resolved next day without any action from my part. It just worked.

kolydart avatar Dec 21 '22 20:12 kolydart

The issue was resolved next day without any action from my part. It just worked.

I did what you said to solve my problem today, but with the expense of not being capable of installing the sounds outside my internal SSD. As soon as I try to change it, same thing happens.

oporapunk avatar Dec 21 '22 22:12 oporapunk

The issue was resolved next day without any action from my part. It just worked.

I did what you said to solve my problem today, but with the expense of not being capable of installing the sounds outside my internal SSD. As soon as I try to change it, same thing happens.

A workaround I tried was the following: move the Muse Sounds directory to the external drive and create a symlink to the new location. It is working fine, with one side effect: you have to have the external drive mounted all the time. If you open a score when the external drive is not mounted, all the playback instruments in the mixer are switched to "MS Basic" SoundFont; if you save the score and you want to use the Muse Sounds Instruments, you have to switch them back one by one. The commands to move and create the symlink are the following: # first, make sure musescore is not running EXTERNAL_VOLUME=/Volumes/change_this_to_your_ssd_name; sudo mv -v ~/Library/Containers/com.muse.hub/Data/InstallData/Instruments ${EXTERNAL_VOLUME}/MuseSoundsInstruments; ln -s ${EXTERNAL_VOLUME}/MuseSoundsInstruments ~/Library/Containers/com.muse.hub/Data/InstallData/Instruments;

kolydart avatar Dec 22 '22 12:12 kolydart

Muse Hub issues are now being handled elsewhere, so will be closed here. If this issue is still valid, please raise it here. You can link to this GitHub issue if it provides useful context or discussion.

its-not-nice avatar Feb 22 '23 17:02 its-not-nice