Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

"Productbuild" won't build a Package

Discussion in 'macOS' started by Unbreakable353, Nov 27, 2015.

  1. Unbreakable353

    Unbreakable353

    Joined:
    Mar 1, 2015
    Posts:
    1
    Hey,

    I want to release a game on the Mac Store and I followed the Unity instructions but the Terminal won't create a package of the game.


    Work-Mac:Mac-AppleStore username$ productbuild --component GAMENAME.app /Applications --sign "3rd Party Mac Developer Installer: DEVNAME" GAMENAME.pkg

    Usage: productbuild [--product <requirements-plist>] {--component <component-path> <install-path>} <product-output-path>
    Build product with a self-contained bundle, e.g. for the Mac App Store

    Usage: productbuild {--content <content-path>} <product-output-path>
    Build product with in-app content

    Usage: productbuild [--product <requirements-plist>] {--root <root-path> <install-path>} <product-output-path>
    Build product with an xcodebuild destination root

    Usage: productbuild [options] --distribution <dist-path> [--package-path <search-path>] <product-output-path>
    Build product with a distribution and the packages it references

    Usage: productbuild --synthesize [--product <requirements-plist>] {--package <pkg-path>} <distribution-output-path>
    Synthesize and write a distribution from component packages

    See productbuild(1) for details.

    That's all I receive from the Terminal.
    The codesign with the entitlements worked but only when I added --deep behind the command.
    I'm using Unity version 5.2.1f1
    Hope someone can help here.
     
  2. FireflyUnity

    FireflyUnity

    Joined:
    Aug 28, 2015
    Posts:
    2
    It might be worth wrapping the .pkg and .app filenames in " ", just in case you have any spaces or special characters in the name, and I'm assuming your DEVNAME contains the app id prefix in brackets (it should automatically be appended to the profile name). This is the command I'm using, for reference:

    productbuild --component "APP NAME.app" /Applications --sign "3rd Party Mac Developer Installer: DEVNAME (APPID_PREFIX)" "APP NAME.pkg"