[Bug]: JASP MacOS does not work for non-admin users

[JorisGoosen]

JASP Version

0.19.3

Commit ID

No response

JASP Module

Unrelated

What analysis are you seeing the problem on?

All

What OS are you seeing the problem on?

macOS Silicon

Bug Description

So all versions of JASP from 0.18 up to 0.19.3 are shown greyed out on a normal user account if installed by the admin.
And trying to run them gives an error.

This issue was supported to us in an email but I can easily reproduce it.
No idea yet what causes it nor why 0.19.1 is the only one that works...

But would be good to fix this.

Expected Behaviour

JASP should be startable by a non-admin-user...

Steps to Reproduce

Install JASP

Log (if any)

No response

More Debug Information

No response

Final Checklist

• I have included a screenshot showcasing the issue, if possible.
• I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
• I have accurately described the bug, and steps to reproduce it.

[github-actions]

@JorisGoosen, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#3399, attaching to an email does not work) a screenshot showcasing the problem, and/or a compressed (zipped) .jasp file or the data file that causes the issue. If you would prefer not to make your data publicly available, you can send your file(s) directly to us, issues@jasp-stats.org

[JorisGoosen]

Looks like there are some differences in permissions, not sure if this is the whole problem but:

[JorisGoosen]

Alright, so this problem can be solved manually by setting the permissions correctly.

• open a terminal as admin
• navigate into JASP-0.19.3.app (or whatever version)
• chmod -r a+r Contents
• chmod -r a+x Contents/MacOS

Now we should just do this during the build

[boutinb]

Find you find it out. Still strange that his 0.19.1 version works.. Should I ask him to set the permissions, or did you already write him?
I suppose this issue can be closed.

[JorisGoosen]

Please dont close this issue until it is fixed.