Search Issue Tracker

Fixed in 2019.1

Fixed in 2018.3

Votes

15

Found in

2018.2.1f1

Issue ID

1065311

Regression

No

[macOS] GameKit reference in the application when Game Center is not used, App Store rejects the build

MacOS

-

Reproduction steps:
1. Open the attached project.
2. Build it as macOS Standalone.
3. Navigate to the "AppName.app" location using Terminal.
4. Input this command (Don't forget to rename the 'AppName' ):
grep -r -i -c "gamekit" "AppName.app"
5. Check the output:

Actual behavior:
- There will be more than 0 references (More than 0 'example:1').

Expected behavior:
- 0 references (Every line says 'example:0').

Reproduced with:
macOS Standalone, iOS
2018.2.0b1, 2018.2.13f1, 2018.3.0b6, 2019.1.0a4

Comments (13)

  1. 509a067290155d97ad7f36dac57a2a27?d=mm

    Oscar-Tsang

    Nov 16, 2018 00:00

    Unity need to face it is a very important. If app (macOS version) do not accept by Apple. The OSX build is meaningless.

    Up to now they still to not have planning to fix this problem. Just reply me it is noted.

  2. 738e3f942996efa04ac7cfc50de689d6?d=mm

    Nananaaa

    Nov 14, 2018 10:51

    Correction to my previous comment:
    Only the Mac OSX build got rejected because it links against GameKit without using it.
    The iOS rejection had a different reason.
    Sorry for that.

  3. 738e3f942996efa04ac7cfc50de689d6?d=mm

    Nananaaa

    Nov 14, 2018 09:48

    Same issue here. Two days ago both iOS and OSX builds got rejected because of:
    Your app links against the GameKit framework but does not appear to include Game Center functionality.
    Unity 2018.2.15f1 was used to create both of them.

    In the past few weeks, two versions (of each iOS and OSX) successfully went through review. All four of those builds were created with Unity 2018.2.13f1.
    Running the command:
    grep -r -i -c "gamekit" "AppName.app"
    Against any of the (OSX) builds that successfully went through review displays:
    "AppName.app/Contents/MacOS/AppName:2"
    So maybe, we're misinterpreting the output of the command.

    In general, Unity 2018.x worked perfect so far. However, the same issue happened once with Unity 5.x and "magically" disappeared after an update.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.