expo sdk53 broke msauth for ios when deploying with azure package deal "Apple App Retailer Launch"

Whereas deploying our expo rn app to the apple retailer utilizing the azure package deal Apple App Retailer Launch, we’re seeing the next error:

Error: [ContentDelivery.Uploader.600003C88200] Validation failed (409) The next URL schemes present in your app are disallowed: [msauth] (ID: <uuid>)

I’ve went by means of a number of solutions about including worth msauth.<my.bundle.id> to the important thing of CFBundleURLSchemes to the .plist file. I am open to any options for any configuration setup I’m lacking…

.plist file

<?xml model="1.0" encoding="UTF-8" ?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist model="1.0">
  <dict>
    <key>technique</key>
    <string>app-store</string>
    <key>teamID</key>
    <string>TEAM_ID</string>
    <key>signingCertificate</key>
    <string>iPhone Distribution</string>
    <key>uploadBitcode</key>
    <false/>
    <key>CFBundleURLTypes</key>
    <array>
      <dict>
        <key>CFBundleURLSchemes</key>
        <array>
          <string>msauth.com.firm.projectname</string>
        </array>
      </dict>
    </array>
    <key>provisioningProfiles</key>
    <dict>
      <key>com.firm.projectname.appname</key>
      <string>UUID</string>
    </dict>
  </dict>
</plist>

Expo’s app.config.js file

module.exports = {
  identify: Demo,
  slug: demo,
  model: "1.0.0",
  scheme: 'msauth',
  orientation: 'portrait',
  icon: './property/photographs/appname/ios-icon-1024x1024.png',
  userInterfaceStyle: 'mild',
  newArchEnabled: true,
  backgroundColor: '#202c5d',
  assetBundlePatterns: ['**/*'],
  ios: {
    icon: {
      backgroundColor: '#202c5d'
    },
    infoPlist: {
      NSCameraUsageDescription: 'Your digital camera will probably be used to scan barcodes or take footage for Demo',
      NSLocationWhenInUseUsageDescription: 'Your places data will probably be used everytime you entry the stock.'
    },
    supportsTablet: true,
    googleServicesFile: './GoogleService-Data.plist',
    bundleIdentifier: 'com.firm.projectname.appname',
    buildNumber: '1.0.0'
  },
  android: {
    adaptiveIcon: {
      foregroundImage: './property/photographs/appname/android-icon-1024x1024.png',
      backgroundColor: '#255d98'
    },
    googleServicesFile: './google-services.json',
    edgeToEdgeEnabled: true,
    package deal: 'com.firm.projectname.appname',
    versionCode: 1
  },
  net: {
    favicon: './property/photographs/favicon.png'
  },
  plugins: [
    ['./plugins/withNinjaLongPaths'],
    ['@react-native-firebase/app'],
    ['@react-native-firebase/auth'],
    ['@react-native-firebase/crashlytics'],
    [
      'expo-build-properties',
      {
        android: {
          minSdkVersion: 26,
          compileSdkVersion: 35,
          targetSdkVersion: 35
        },
        ios: {
          useFrameworks: 'static'
        }
      }
    ],
    [
      'expo-image-picker',
      {
        photosPermission: 'Allow $(PRODUCT_NAME) to access your photos',
        cameraPermissions: 'Allow $(PRODUCT_NAME) to access your camera'
      }
    ],
    [
      'expo-location',
      {
        locationAlwaysAndWhenInUsePermission: 'Allow $(PRODUCT_NAME) to use your location.'
      }
    ],
    [
      'expo-splash-screen',
      {
        ios: {
          backgroundColor: '#202c5d',
          image: './assets/images/appname/splash-1024x1024.png',
          imageWidth: 200
        },
        android: {
          backgroundColor: '#202c5d',
          image: './assets/images/appname/splash-1024x1024.png',
          imageWidth: 200
        }
      }
    ]
  ]
};

A couple of screenshots of azure devops pipelines for context

Word: we’re in a position to deploy to firebase okay, and google playstore okay, simply the apple retailer retains rejecting our app.

If every other data is required, please make a remark and I’ll edit this query. Thanks.