Does "Automatically add capabilities" checkbox work properly when it's turned off?

Unity Engine
1

Hello everyone.

I’ve been trying Unity2018.3.11 and the project includes “NotificationServices” code.
I don’t want Notification capability to be automatically enabled in Xcode project,
so I turned “Automatically add capabilities” checkbox off in Player Settings and
build Xcode project.

After I opened the Xcode project, I figured out that “Bundle Identifier” was replaced as ‘jp.co.xx.Unity-Target-New’ somehow,
and Xcode project build doesn’t work.
Part of the error is bellow:

Does anyone have same problem?

2

I have been having issues with this too. I noticed the Automatically add capabilities wasn’t available on 2018.3.8f1 so I updated to 2018.3.10f1 (Now the option is available in Player Settings UI, but not accessible in code).

Just did a Jenkins build and it failed because of this. Added “Unity-Target-New” at the end, same as you.

Really frustrating.

3

At a quick glance it seems to be storing the bundle id in the Info.plist as

    <string>bundleIdBeforeLastPeriod.${PRODUCT_NAME}</string>

I’m guessing it’s XCODE that’s resolving PRODUCT_NAME to Unity-Target-New, and that something tied up with their auto-capabilities setting re-defines that variable (where it was previously static or the build process was structured differently).

I don’t have time to look into this now, but it seems like this capabilities feature wasn’t tested beyond generating an XCODE project. I’m also weirded out how it’s not accessible in code nor consistently supporting along 2018.3.x. Oh well just one of those Unity things.