Error using wildcard App ID

Expo Development Tools
1

Hello,

I’m getting the following error while building my iOS application using a wildcard app id:

Error: validateProvisioningProfile: wrong bundleIdentifier found in provisioning profile; expected: ca.fastlanetestapp.testApp1, found (in provisioning profile): ca.fastlanetestapp.*
    at _ensureBundleIdentifierIsValid (/usr/local/turtle-js/node_modules/xdl/build/detach/IosCodeSigning.js:287:11)
    at Object.validateProvisioningProfile (/usr/local/turtle-js/node_modules/xdl/build/detach/IosCodeSigning.js:266:3)
    at Object.<anonymous> (/usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:73:53)
    at Generator.next (<anonymous>)
    at step (/usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:52:191)
    at /usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:52:361
    at <anonymous>

My understanding is that by using a wildcard app id such as ca.fastlanetestapp.* I would be able to build more than one application. In this case I’m trying to build an application using the ca.fastlanetestapp.testApp1 id.

2

I tried to use an app id without wildcards and now I’m getting this error:

Error: validateProvisioningProfile: wrong bundleIdentifier found in provisioning profile; expected: ca.fastlanetestapp.testApp1, found (in provisioning profile): ca.fastlanetestapp.testapp1
    at _ensureBundleIdentifierIsValid (/usr/local/turtle-js/node_modules/xdl/build/detach/IosCodeSigning.js:287:11)
    at Object.validateProvisioningProfile (/usr/local/turtle-js/node_modules/xdl/build/detach/IosCodeSigning.js:266:3)
    at Object.<anonymous> (/usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:73:53)
    at Generator.next (<anonymous>)
    at step (/usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:52:191)
    at /usr/local/turtle-js/node_modules/xdl/build/detach/IosIPABuilder.js:52:361
    at <anonymous>

I’ve read the comments here where they say this might be an Expo bug that has already been fixed but apparently the problem is still present.

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.