Invalid Provisioning Profile when submitting to App Store

[BusFactor1Inc]

When I try to submit to the App Store, I get the following error:

ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ca.busfactor1.location [Payload/Location.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."

Has anyone successfully submitted a LN app to the App Store before? Everything seems fine with the app during development with installation and running on an actual phone.

[mgorges]

There are a few published apps, which are build using LambdaNative, e.g. RRate, uSquish, telePORT by our team, and I believe The Death of the Corpse Wizard by @VincentToups.

Did you compile in release mode before submitting with Application Loader?

[BusFactor1Inc]

Building in Release gives the following error:

=== BUILD TARGET Location OF PROJECT Location WITH CONFIGURATION Release ===

Check dependencies
Code Signing Error: Location has conflicting provisioning settings. Location is automatically signed for development, but a conflicting code signing identity iPhone Distribution has been manually specified. Set the code signing identity value to "iPhone Developer" in the build settings editor, or switch to manual signing in the project editor.
Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.1'

** BUILD FAILED **

I think I've generated the proper certificates AFAIK according to the Xcode dialog. Not sure where to go from here...

[mgorges]

Could you retry by manually removing the "-allowProvisioningUpdates" in targets/ios/build-binary which were added in commit e331083 to see if that is the problem?

[BusFactor1Inc]

I tried that but still the same error.

[BusFactor1Inc]

By creating a Wildcard provisioning profile on developer.apple.com I was able to get the .ipa to sign correctly. I think it was a mix up with the app identifier.

[mgorges]

So the issue is in the code I added in 7155c9c not selecting the right one?

[BusFactor1Inc]

I'm not entirely positive if that was it as I tried playing with that code a bit before reverting.

I think it hd to do with the app identifier but I'm not positive. This code signing is a bit of Black Magic to me, but I did manage to get it working and uploaded into the store. I had some old profiles lying around which were not being selected, but after I created the wildcard profile, the line:

using provisioning profile [...]

did have a profile printed, as opposed to before where there wasn't one before.

[mgorges]

The idea of the 7155c9c code was that it selects the first Distribution profile it encounters, as get-task-allow has to be false for those. I am wondering if it either didn't find one of those at all, or picked the wrong one?

[mgorges]

Was this resolved, and we can close this, or is this still something we need to look into?