Numerous issues with iPad and Mac apps

Support & Troubleshooting
1

1. Summary/Title
numerous issues upon first install

2. Steps to Reproduce
Provide step-by-step instructions to reproduce the issue.

  • Try to control an app
  • reboot
  • Launch meta server

3. Expected Result
That it works properly

4. Actual Result
It doesn’t work properly
I keep getting a message that metagrid needs accessibility permissions despite it already having those permissions
I’ve tried deactivating and reactivating the permissions, rebooting both the Mac and the iPad ,

Nothing works
Every time I tap on a button in metagrid on iPad, the Mac says metaserver needs accessibility permissions On Mac. Of course it does have those permissions.
Also, meta server does not start automatically on reboot in macOS, I have to manually launch it
Also, the link to the forums in the metagrid iPad app is broken

5. Screenshots or Video (if applicable)
Attach any visuals that may help clarify the issue.

6. Device Information

  • Operating System (OS version): iPadOS 26.
  • MetaGrid Pro version: 1.6
  • Device Model (e.g., iPad, Mac): iPad and Mac.
  • Affected software version (e.g., Cubase 14): anything

7. Additional Notes
Any other relevant information.

2

You need to restore the permissions for MetaServer:

https://metagrid.zendesk.com/hc/en-us/articles/31480781739281-How-to-reset-accessibility-permissions-on-Mac

3

Solution number one doesn’t work.

Solution number two will reset all my apps correct?

This is a new install on a new laptop so I don’t know why I would have to reset the permissions.

4

So it seems that MetaServer doesn’t have the required permissions - can you please confirm it is located in Applications folder?

5

It is in the application folder. This happens on both my MacBook and Mac mini, the same exact behavior.Both on Macos 26.
I have log files and a video but I can’t upload them.

6

Ok… my bad. I actually read the instructions for option 1 carefully and followed them. That solved the issue.

Before, I was just detecting the accessibility button. Actually removing Metaserver from accessibility and re-adding it did the trick.

7

Glad you have managed to make it work. Closing this topic.