Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
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
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
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.