JASP 0.98.1 Won't Open on Apple Silicon Mac: 2026 Troubleshooting Guide

JASP provides a separate Apple Silicon download path. Therefore, a launch failure is not proof that the processor is unsupported. The first decision is whether the failure occurs before the app starts, during startup, or only when a project or analysis module loads.

Use the symptom below as your first routing rule:

• Download stops or the file is unusually incomplete: investigate the browser transfer and package integrity.
• The DMG does not mount: treat the installer as damaged or incomplete. Do not continue to security exceptions.
• macOS displays an internet, developer, or notarization warning: identify the exact warning and use Apple’s permitted approval path.
• The icon is clicked but no window appears: collect launch and Console evidence before deleting files.
• JASP opens and immediately quits: test account configuration, caches, and a clean user.
• JASP opens with a blank project but fails on one .jasp file: isolate the project, filter, computed column, or analysis module.
• The entire Mac becomes slow or unresponsive: inspect CPU, memory pressure, disk activity, and the process state before repeating the launch.

Write down these facts before changing anything:

• JASP version shown by the downloaded package or application.
• Mac chip type.
• macOS version.
• Exact installer filename.
• Whether the failure affects a blank launch or only a saved project.
• The last successful action and the first failed action.
• Whether the Mac is personally managed, lab-managed, or controlled by university policy.

This record prevents a common mistake: treating a project-file failure as an application failure.

The official JASP download page is the source of truth for the available builds. As of the stated review date, the official material identifies JASP 0.98.1 and lists an independent Apple Silicon download option. The official citation information gives the release date as June 2, 2026. Website pages can update at different times, so verify the live download entry and package information before reporting a version issue.

Use this installation check:

• [ ] Open the official JASP download page, not an unknown mirror.
• [ ] Select the Apple Silicon package for an Apple Silicon Mac.
• [ ] Keep the original download until the application launches successfully.
• [ ] Confirm that the DMG mounts without an error.
• [ ] Copy JASP to the Applications folder.
• [ ] Eject the DMG only after the copy finishes.
• [ ] Launch the copied application from Applications.
• [ ] Record the result and any exact alert text.

A failed download leaves different evidence from a security block. A browser may show a finished transfer while the DMG still fails to mount. A mounted DMG does not prove that the application copy completed correctly. A copied application that launches but crashes later points to a different layer.

If the DMG will not mount, download it again through the official page and compare the result of the new transfer with the first attempt. If the second file also fails, preserve the filenames and error messages. Report the issue with the download environment, browser, network, and package name instead of repeatedly opening the damaged file.

If the DMG mounts but copying fails, check available storage and destination permissions. Do not assume that a permission error means you need to weaken system protection. A managed Mac may restrict application installation even when the account appears to have normal access.

macOS security prompts are not interchangeable. A normal first-run confirmation, a warning about an unidentified developer or notarization, and a university management restriction require different handling.

Use Apple’s Gatekeeper and runtime protection documentation to identify what macOS is checking. The safe sequence is:

• Read the complete alert.
• Confirm that the application came from the official JASP source.
• If the source cannot be verified, stop.
• If the source is verified, use the approval action Apple documents for that alert.
• If the control is enforced by a school profile, contact the university administrator.
• Record the policy message instead of attempting to bypass it.

Do not disable Gatekeeper globally. Do not disable System Integrity Protection. Do not use an unknown command copied from a forum to force the application open. Those actions remove useful protection and can make the later support record less reliable.

Stop condition: If you cannot prove where the JASP package came from, or if the device is managed by your institution, do not create a security exception. Preserve the alert and ask the administrator to validate the package and policy.

A Mac can also show a prompt because an application was downloaded from the internet. That is not the same as a blocked application under a managed configuration. The distinction matters for campus support: one may be resolved through an approved user action, while the other needs an administrator’s policy decision.

When JASP quits immediately, avoid deleting its folders as the first response. Configuration, cache, module state, and permissions can all be relevant evidence. A reset may make the application launch, but it can also remove information needed to explain the failure.

First, reproduce the crash once and note the exact sequence. Then collect:

• The JASP version and package architecture.
• The macOS version and chip type.
• The time of the crash.
• Whether the crash occurs with no project open.
• Whether the account is a standard or managed university account.
• The visible alert, if any.
• A crash report from Console.

Apple’s Console report guide explains how to locate and review system reports. Preserve the original report as a file. Do not paste private project data into a public issue unless it has been removed.

Next, create a controlled account test if your local policy permits it. A new macOS user account is not a repair; it is an isolation test.

• Launch JASP from the new account.
• Use a blank workspace.
• Do not open the thesis project yet.
• Check whether the application remains open.
• Record whether the result differs from the original account.

If JASP works in the new account, the evidence points toward the original user profile, configuration, cache, permissions, or module state. If it fails in both accounts, investigate the installation, device policy, operating system, or an application-wide issue.

GitHub reports can help you recognize possible directions, but the JASP issue tracker contains user reports and individual cases. A report about a crash or resource problem is not confirmation that JASP 0.98.1 has a universal defect. Match any report by operating system, chip, build, reproduction steps, and project characteristics.

A .jasp file can fail even when the application itself is healthy. This is especially important when a blank project opens normally.

Protect the source first:

• [ ] Stop opening the only original repeatedly.
• [ ] Make a read-only backup.
• [ ] Work on a copy with a clear filename.
• [ ] Remove identifying data from any sample used for support.
• [ ] Test a blank JASP project.
• [ ] Test a small de-identified dataset.
• [ ] Test the copied problem project.
• [ ] Compare the result after each stage.

The result creates a useful branch:

• Blank project fails: continue with application, account, policy, or resource diagnostics.
• Blank project succeeds but sample data fails: inspect the data format and analysis path.
• Sample succeeds but the old project fails: investigate the project structure.
• The project opens but one analysis fails: isolate the module, filter, computed column, or variable transformation.

Older project files are not automatically unrecoverable. However, repeated upgrades, incomplete saves, unusual filters, calculated columns, or a specific analysis module may create a trigger that is not present in a blank workspace. Do not promise recovery before testing the copy.

Once the file opens, verify the research output rather than stopping at the first visible window. Check that the result tables render, graphs appear, analyses retain their options, and exported files contain the expected content. A project that opens with missing output is not a successful recovery.

A launch stall can be caused by a busy process, memory pressure, disk activity, or a module that does not complete initialization. It can also be a symptom of a broader Mac problem. Avoid calling the issue a “JASP memory bug” without evidence.

Open Activity Monitor while reproducing the problem. Apple’s process information guidance describes the information available for running processes.

Record observations rather than unsupported performance claims:

• Whether the JASP process appears.
• Whether CPU use changes during launch.
• Whether memory pressure is green, yellow, or red.
• Whether disk activity continues.
• Whether another process consumes the available resources.
• Whether the application eventually responds or quits.
• Whether the same behavior appears in a blank user account.

Do not treat a high resource reading as proof of a defect. One large dataset, a complex model, or an analysis module can behave differently from a blank project. If the Mac becomes unstable, stop the test, save the evidence, and avoid launching the same project repeatedly.

For a campus-managed Mac, resource restrictions may be deliberate. A security agent, storage quota, or device policy can affect installation and execution. That is a machine administration question, not something to solve by removing protections.

A clean remote Apple Silicon Mac is useful when you lack administrator access, the lab Mac has unknown configuration, or a paper deadline makes local isolation impractical. It should be a diagnostic control, not an excuse to upload identifiable research data to an unapproved environment.

Use the same sequence on the remote machine:

• Confirm the Mac chip and macOS version.
• Download the official Apple Silicon JASP package.
• Record the package filename and JASP version.
• Install JASP in the normal Applications location.
• Launch a blank project.
• Run a minimal analysis with de-identified data.
• Save the project copy.
• Export a result file.
• Compare every outcome with the local test.

The comparison should include the application build, macOS version, project copy, launch result, analysis result, saved file, and export. Keep the local and remote evidence separate. Do not change multiple variables at once.

Your decision can follow this comparison:

Repair the local Mac when:

• The remote test succeeds.
• The local failure is limited to one account, policy, package, or project.
• You have administrator or campus support access.
• The local machine is approved for the data and deadline.

Move the short-term task to a remote Mac when:

• The remote clean test succeeds.
• The local machine cannot be reset or approved quickly.
• You can use de-identified data or an institution-approved workflow.
• You have a clear download and delivery method for the final outputs.

Return to a stable version or submit an official report when:

• The same clean reproduction fails across approved environments.
• The package source and architecture are correct.
• A blank project fails before any research file is opened.
• The issue tracker or official support channel needs a complete reproduction record.

Before using CALMVPS for research work, review the remote Mac service overview and confirm that the planned connection method, storage workflow, and institutional data policy are acceptable. A remote session does not automatically make restricted data eligible for external hosting.

A working launch is only the first gate. Before you move a paper analysis, use this acceptance checklist:

• [ ] JASP launches without opening the original project.
• [ ] A blank project remains stable.
• [ ] A de-identified sample analysis completes.
• [ ] The problem project copy opens, or the failure is documented.
• [ ] Result tables match the expected analysis settings.
• [ ] Graphs render correctly.
• [ ] The project saves to the intended location.
• [ ] Exported results open in the required format.
• [ ] Data and output permissions match institutional policy.
• [ ] The recovery path is written down for the next lab member.

If you need to estimate the commercial route, use the CALMVPS pricing page only after confirming that a temporary remote environment fits your data policy. The relevant comparison is not simply “local versus remote.” It is whether the remote option gives you a clean, reproducible control without creating an unapproved data-handling path.

Use these lists as the decision tool for the next action.

Continue repairing the local Apple Silicon Mac if:

• The official package installs correctly.
• Gatekeeper permits the verified application through an approved path.
• JASP works in a clean user account.
• The failure is tied to one project or module.
• Your institution requires all research data to remain on local or campus-managed storage.

Use a temporary CALMVPS Mac for controlled reproduction if:

• You need a clean environment to distinguish software from local configuration.
• You have no administrator rights on the lab device.
• The analysis can use de-identified data.
• You need a short-term macOS environment while campus support investigates.
• You can retrieve and verify the final project and exported results.

Do not use either route yet if:

• The installer source is uncertain.
• The Mac is subject to a policy you have not cleared.
• The project contains restricted or identifiable data that cannot leave the approved boundary.
• You have not made a read-only backup.

The remote option is not the best long-term answer for every laboratory. A permanently heavy workload, strict physical-device requirements, offline operation, or sensitive data policy may justify a university-managed Mac or a purchased machine. For a short paper deadline, however, a clean temporary environment can answer the key diagnostic question faster than repeatedly changing an unmanaged local installation.

Why can a completed JASP download still fail to open on a Mac?

A completed browser download does not prove that the DMG is intact or that the application copied correctly. Check whether the disk image mounts, whether the app can be copied to Applications, and whether the package came from the official JASP download page. A damaged archive, interrupted transfer, or wrong processor build can fail before JASP displays a useful message.

Which JASP build should an Apple Silicon Mac use?

Use the native Apple Silicon build when the official JASP download page offers it for your Mac. Do not select the Intel package merely because an older tutorial recommends it. Keep the downloaded file until the first launch succeeds, and record the package name, JASP version, macOS version, and chip type in your support notes.

What evidence helps diagnose an immediate JASP crash?

Record the exact launch time, visible alert, JASP version, macOS version, chip type, and whether the crash occurs before a project opens. Then review the crash report in Console and check the process state in Activity Monitor. Preserve the report without editing it. A clean-user test can separate account configuration problems from an application-wide failure.

Can an older JASP project be recovered if it will not open?

Usually, the first priority is to protect the original file, not to repeatedly open it. Make a read-only copy, test a blank project, then try a de-identified sample and the copy of the older file. If only the project fails, inspect filters, computed columns, and the analysis module. Never overwrite the sole original during recovery.

How can you test JASP without another physical Mac?

Reproduce the installation on a clean remote Apple Silicon Mac with a blank workspace and de-identified data. Compare the application build, macOS version, project file, launch result, analysis output, save operation, and export file with the local attempt. If the remote test succeeds, the evidence points toward the local account, policy, installation, or machine rather than a general JASP failure.

If your current lab setup is blocking a paper, it may be the weaker long-term path for this specific deadline: a managed Windows or Linux workstation cannot provide the same native macOS test, a shared lab Mac may have unknown configuration, and repeated local resets can risk your working environment. After the clean test passes, renting a CALMVPS Mac by the week or month gives you a controlled Apple Silicon environment for temporary JASP validation without committing to a new physical Mac.

For the safest handoff, use de-identified data, verify the project and export files, and then decide whether to continue the short rental or return to repairing the laboratory machine. You can review the CALMVPS remote Mac ordering options when the environment, data policy, and recovery plan are already clear.