Skip to main content
Question

MyViewBoard (ViewSonic) — VPP/Self Service install succeeds and consumes a license, but app won’t launch (iOS app on Apple Silicon Mac)

  • Oct 8, 2026 6:45 PM UTC
  • 2 replies
  • 59 views

jschantli
Forum|alt.badge.img

We’re deploying MyViewBoard (free, Mac App Store) to Apple Silicon Macs via Jamf’s VPP “Mac Apps” distribution. The install reports success and a license is consumed, but the app won’t launch — [I get either no feedback when I open the app or I get a message telling me the app cannot be opened]. If a user instead opens the App Store themselves and clicks “Get,” it installs and works fine every time.

The app is a Designed for iPad app but can work on Apple Silicon.

Has anyone run into this with MyViewBoard, or with other App Store apps that are iPadOS binaries running on Apple Silicon Mac? Curious if there’s a known fix or workaround for getting this working with JAMF Self Service since our users don’t have Apple IDs with their macs unless they use their personal one.

2 replies

Forum|alt.badge.img+3
  • New Contributor
  • Oct 22, 2026 7:09 PM UTC

I’m having a similar issue with myViewboard. It shows it installs but installs a Runner.app that has the icon but doesn’t actually work. I tried to do it via self service instead of autoinstall and it shows up but just spins and spins. Just to be sure my Mac App store app that I’ve manually set from the iPad app shows this:

Name myViewboard

Version: 3.10.204.30102042

Bundle Identifier: com.viewsonic.droid


jschantli
Forum|alt.badge.img
  • Author
  • New Contributor
  • Oct 26, 2026 8:12 PM UTC

I’m having a similar issue with myViewboard. It shows it installs but installs a Runner.app that has the icon but doesn’t actually work. I tried to do it via self service instead of autoinstall and it shows up but just spins and spins. Just to be sure my Mac App store app that I’ve manually set from the iPad app shows this:

Name myViewboard

Version: 3.10.204.30102042

Bundle Identifier: com.viewsonic.droid

Looks like we are having the same issue. I did create a ticket with ViewSonic about this and am just waiting for them to get back to me. Last a heard from them they are contacting the dev team about this issue.