Projects won't open on Unity 2023 or Unity 2022 on macOS

Unity Engine
,
1

Unity projects can’t be opened on macOS using Unity 2022 or Unity 2023. It works on Unity 2021 and lower only.

I get this

9414206--1318709--upload_2023-10-17_9-56-38.png
9414206--1318709--upload_2023-10-17_9-56-38.png832×270 32 KB

and it never verifies. Please fix this, I am surprised this is still an issue.

2

Is anything in the editor.log that may help?

3

I also created a bug report but I can’t see it Jira Service Management

4

This is macOS verifying the hash of the Unity app. This is done before any of Unity’s code is run and is entirely related to macOS, there’s nothing Unity can do to influence the process.

This happens the first time a new app is opened. You must have installed / updated Unity 2022 and 2023 recently and they haven’t been verified yet, while Unity 2021 has previously passed verification and doesn’t need to be verified again.

How long have you waited for the verification to complete? The Unity app bundle is big and, depending on your drive speed and current load, verification can take dozens of minutes. Also try to restart to make sure there’s no stuck system service.

As a last resort (though I’d advice against it), you can remove the quarantine attribute on the app bundle to skip verification by executing this in the Terminal (and replacing PATH_TO_UNITY with the actual path to the Unity app bundle):

xattr -rd com.apple.quarantine PATH_TO_UNITY
5

There is another forum thread about the problem. This is a Unity issue…

How long have you waited for the verification to complete? The Unity app bundle is big and, depending on your drive speed and current load, verification can take dozens of minutes. Also try to restart to make sure there’s no stuck system service.

The verification popup eventually disappears but the project doesn’t open. See the other forum thread…

6

Those are separate issues. The verification happens before Unity’s code is executed and before any bug on Unity’s side could sneak in. The linked issue happens during launch and is an issue in Unity’s code. The verification might happen before the issue on Unity’s side is triggered but the likelihood of the verification and Unity’s issue being linked is extremely small.