musescore / musescore/MuseScore

"An update for MuseSounds is available" dialog appears on launch with no clear way to resolve

Open
#32,796 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

MuseSounds needs review UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

On launching MuseScore, a dialog box now appears about an update to MuseSounds:

An update for MuseSounds is available

To keep MuseSounds running smoothly, MuseScore Studio needs to close briefly so MuseHub can apply the update. You'll be prompted to relaunch MuseScore Studio when it's ready.

Despite the message, clicking the "Quit & launch MuseHub" button does not seem to apply any sort of update, it merely opens the MuseHub website. Relaunching MuseScore just shows the same message again; no update seems to have been applied. Dismissing it with "Not now" allows me to use the application as normal.

Issues:

  1. The link just takes you to the MuseHub webpage (https://www.musehub.com/). It's not clear what you need to do from here
  • If it's possible to install the MuseSounds update manually, it's not clear how or which package should be downloaded. There are many options, most of which cost money.
  • If the MuseHub desktop application is required, there should be clearer instructions on this. MuseScore should detect this and send you directly to the download page.
  1. If the user does not want to install this update, there should be an option to ignore it, instead of being nagged every time on startup.
Supporting files, videos and screenshots
Image
In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

I was unable to check

Operating system

macOS 15.7.4

Additional context

I do not have the MuseHub desktop app installed

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.