Support

We respond to every support request personally.

Please include your macOS version + whether you're using the Mac App Store or the direct download (.pkg) version, so we can reproduce.

Common questions

The Mac app won't open after install

If macOS shows a Gatekeeper warning ("Jamverse can't be opened because the developer cannot be verified"), you likely have an older PKG. Re-download the latest from downloads.jamvers.com. The current PKG is signed by Apple Developer ID and notarized — you should not see a warning.

I'm on the Mac App Store version — where's my Creator tier?

The Creator subscription (presets, mixer/producer editing, marketplace publishing) is rolling out in a future release. The current build serves the Jammer tier to every install.

The web app at jamvers.com/jam doesn't show what I expect

The web client is currently a preview of the shared design surface. Audio features (mic input, chord detection, jam playback) are part of a later release. The Mac app at this point has the full audio pipeline.

Is there a Windows version?

Not yet. The architecture (pure-C++ engine + JUCE shell + Vite web) is portable; Windows is a planned target after Sprint 1.

How do auto-updates work?

The direct-download Mac app uses Sparkle for in-app updates and will offer new releases automatically when launched. The Mac App Store version uses Apple's built-in update mechanism (App Store → Updates tab).

Bug reports

If you hit a bug, please include in your email:

Steps to reproduce
macOS version (Apple menu → About This Mac)
Jamverse version (Jamverse menu → About Jamverse)
Distribution channel (Mac App Store / direct PKG)
Console.app log excerpt filtered by "Jamverse" if relevant

Feature requests

Email the same address with the prefix "[Feature]". We read everything but reply with a real ETA only for things on the active roadmap.

← Back to Jamverse