Build for Xcode?

Unity Engine
,
1

Hi guys,
I am prepping a build, for Mac OS, that I want to allow people to play outside of the App Store. My issue is that, my build from (Stand Alone, For Mac OS), did not create a file that I can open in Xcode, just one that now opens from my desktop.

I am under the impression that in order to have a file that can be played on any ones Mac OS, that I must validate an archive which has the proper certificate.

Any ideas?

2

True (but not relevant).

You don’t have to, but users will get scary warnings and have to know how to override them otherwise.

So, yes, the next step is code-signing your app. You don’t need to build from Xcode to do this, you can do this with the codesign command on the command line (or in a shell script). Use man codesign to learn about this tool, or read the Unity manual, just skipping any bits which are obviously related to the Mac App Store.

3

Basically:

codesign --deep --sign "Your Identity" whatever.app

But it’s strongly recommended you digest this:

4

I included the bundle ID in the Player Settings under Mac OS. Its just that I was expecting to be able to open the build in Xcode like I would for an iOS build.

?

5

Xcode doesn’t enter into the picture. You just codesign from the command line. I.e. outside both Xcode and Unity.

1 Like
6

So the fact that this line ()bundle ID, Mac OS) is filled correctly, anyone who downloads this, from GameJolt.com, will be able to open it, with out restrictions on their Mac?

7

Nope. You still need to get it past GateKeeper the usual way; either disable it entirely, or right-click and click Open. But that’s basic macOS use now :slight_smile:

8

I am not sure that is true.
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html

This is what I was expecting.

9

You have three levels of app signing on macOS:
1.Unsigned. These are allowed if the system is set to allow unidentified developers. I.e. effectively GateKeeper turned off. They’ll still run on the system they were built on, as your own apps are automatically blessed.
2.Third-party develop signing. This is the outside-the-store option for pretty much anyone sensible. The system might still block these if set to only allow MAS apps, and you still might need to right-click the app and choose Open on the first run after downloading it to a new system.
3.MAS signing. Pre-approved. Blessed. Angels sing when they launch.

1 Like
10

So I am looking at 2, and am hoping that the preferences are set to allow MAS and certified developers.

If so, is including the bundle ID, I the unity build settings, Mac OS, good enough?

Praying for angles.

11

Your preferences don’t matter. It’s the end-user’s which do. I think the default now is the middle-ground, but people still need to right-click and select Open from the context menu to launch the first time.

This page should have everything:
https://docs.unity3d.com/Manual/HOWTO-PortToAppleMacStore.html

12

Thanks

thanks… I hope it’s that I’m just waking up. But that page worries me. I’m terrible at back end stuff.