imuximux
AI workbench for macOS

Mobile update channels

Clavue ships two phone apps with two JSON channels. Publishing the wrong binary to the wrong manifest breaks auto-update and store compliance. Always verify bundle id before upload.

Two channels

Pick the manifest that matches the product you ship.

  • Clavue Mobile — com.clavue.xw — latest-mobile.json — hub /mobile#clavue
  • imux Mobile — com.imux.mobile — latest-imux-mobile.json — hub /mobile#imux
  • Desktop imux — latest.json + Sparkle (NOT mobile manifests)
  • Clavue GUI — latest-gui.json (NOT mobile manifests)
# Clavue Mobile
curl -s https://www.clavue.com/downloads/mobile/latest-mobile.json

# imux Mobile
curl -s https://www.clavue.com/downloads/mobile/latest-imux-mobile.json

Hard rules

From docs/product-identity.md — enforced in release scripts.

  • Never publish imux-mobile binaries into latest-mobile.json
  • Never publish Clavue Mobile binaries into latest-imux-mobile.json
  • Never upload an IDE .pkg to ASC app 6798073173 (that listing is imux Mobile only)
  • Check /mobile before sideloading — section headers match bundle id

Verify before install

Users should confirm product name, bundle id, and manifest URL on the mobile hub.

Troubleshooting

If auto-update installs the wrong app, you subscribed to the other product manifest.

  • Auto-update pulled wrong app — you subscribed to the other manifest; reinstall from correct /mobile# section
  • Version mismatch with desktop — imux Mobile requires desktop protocol 2; upgrade Mac/Windows imux
  • IPA vs APK — each manifest lists platform-specific artifacts; read notes field

Next