Mac Store - Game Centre Entitlement Problem

As described in this thread by others - http://forum.unity3d.com/threads/ur...cted-because-gamekit-framework-linked.261354/ - our game was uploaded to the Mac app store recently with no problems, but a few weeks later, they have changed their admission policy, and reject the game's update. Seemingly Unity automatically includes the GameKit framework, and Apple will not accept that being used without adding the Game Centre entitlement.

So as a solution to appease Apple, we added Game Centre to the Mac store version, so we could add the entitlement without getting further rejections. However upon adding the entitlement "com.apple.developer.game-center", codesigning and creating an installer via command line, and attempting to upload this update via application loader, it fails with the following messages:

Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile: 'com.apple.developer.game-center' in '[app name].app/Contents/Frameworks/MonoEmbedRuntime/osx/libMonoPosixHelper.dylib'.

Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile: 'com.apple.developer.game-center' in '[app name].app/Contents/Frameworks/MonoEmbedRuntime/osx/libmono.0.dylib'.

Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile: 'com.apple.developer.game-center' in '[app name].app/Contents/MacOS/[app name]'.

This is baffling, as our provisioning profile definitely claims to have Game Centre enabled when looking at Apple's Mac developer centre, and this does seem confirmed by the profile, when opened in a text editor, containing:
<key>com.apple.developer.game-center</key>
<true/>

Removing the entitlement before codesigning lets it upload with no problem. But of course Apple will just reject that. Does anyone else have a similar or related problem, or a solution?

 

The problem, how do you solve it?

 

Finally I found solution... Just add your embedded.provisionprofile to Content folder. You can create and download provision profile in Apple developer console.

 

Thanks! This solution worked perfectly!

 

Thanks somealexander for your response. It's useful.