Context
We are using Azure DevOps to build and deploy a MAUI-IOS application to Testflight at the moment utilizing a few pipelines that is working perfectly. However I need to introduce additional apps to support a multi-environment setup (DEV,UAT,PRD). This requires separate app builds that point to separate API's depending on environment. So we have the following apps:
- com.acme-dev.app
- com.acme-uat.app
- com.acme.app (prd)
Problem
I setup a new App in AppStore and I updated all the variables I could find in the source code but for some reason when publishing, the app is still published to the original app in TestFlight.
I updated the ApplicationId and ApplicationIdGuid properties in the .csproj for the build step. Verified that parameters are correct in the resulting .ipa's Info.plist:
- CFBundleIdentifier set to the new App
- CFBundleDisplayName set to the new App
Then when executing the DevOps task (Apple App Store Release task) to publish the ipa to TestFlight, I can see that the fastlane command is utilizing the correct details:
[command]/usr/local/lib/ruby/gems/3.0.0/bin/fastlane pilot upload --api_key_path /Users/runner/work/_temp/api_key.json -i /Users/runner/work/r1/a/deploy/AcmeApp.ipa -a com.acme-uat.app -p 3449341595
Where -a is the BundleId from AppStore and -p is the AppleId.
I am sure I am missing a setting somewhere but for the life of me can't find it. And I am baffled why fastlane would upload to the incorrect app even though it has a set of parameters pointing it to the correct one?
(I also created a new Provisioning Profile pointing to the new BundleId during upload)
Any help of ideas would be appreciated.
Tried updating all relevant ios parameters I could find.