Use two NFC entitlement in the same App

Hello, I have developed an iOS application called DinecTag (be.dinec.DinecTag) with a developer account named Dinec International which is registered in Belgium, I received the NFC entitlement valid for Europe and my App is on the App store since some months (the App is used to open doors by presenting the iPhone in front of a special reader) The App is published only on countries inside Europe (it don’t work outside anyway)

I would like my App can be used outside Europe, so I need another entitlement called NFC & SE Platform entitlementn to ask for that, I need an account registered in a country covered by that entitlement

Dinec is a company that is member of the Lisam group

Lisam has an apple developer account registered to USA, called Lisam Systems

So I have asked to the owner of that account to add me as a developer in the USA team

So when I connect to my developer account, I can switch between Dinec International SA and Lisam Systems on top right of the screen, I am member of the two teams.

I would like to avoid if possible to create a second application, can you confirm it is possible in my case ?

What are the next steps ?

Best regards

Jean-Paul Deryck

Answered by DTS Engineer in 863281022
I would like to avoid if possible to create a second application … ?

I don’t see how that’d be possible. You want to ship two different variants of your app:

  • One with the EU entitlement, only in the EU, authored by your EU-based organisation.
  • Another with the non-EU entitlement, in various countries outside the EU, authored by your US-based organisation.

App Store Connect doesn’t support that. In ASC:

  • A given app record is ‘owned’ by a specific team, whereas you want to associate it with multiple teams.
  • And you can only add a single binary to that an app record [1], whereas you want to add multiple binaries.

So, you’ll need multiple app records in App Store Connect, each with its own App ID.

Of course these two apps will share a lot of same source code. Usually I’d set this up by duplicating the app target in Xcode and then tweaking the build settings, most critically the bundle ID, on that second target.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] I’m talking about the current binary. You can add additional binaries as you update the app, of course.

Accepted Answer
I would like to avoid if possible to create a second application … ?

I don’t see how that’d be possible. You want to ship two different variants of your app:

  • One with the EU entitlement, only in the EU, authored by your EU-based organisation.
  • Another with the non-EU entitlement, in various countries outside the EU, authored by your US-based organisation.

App Store Connect doesn’t support that. In ASC:

  • A given app record is ‘owned’ by a specific team, whereas you want to associate it with multiple teams.
  • And you can only add a single binary to that an app record [1], whereas you want to add multiple binaries.

So, you’ll need multiple app records in App Store Connect, each with its own App ID.

Of course these two apps will share a lot of same source code. Usually I’d set this up by duplicating the app target in Xcode and then tweaking the build settings, most critically the bundle ID, on that second target.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] I’m talking about the current binary. You can add additional binaries as you update the app, of course.

Use two NFC entitlement in the same App
 
 
Q