[match] provisioning profile generated via match blocks release installation on TestFlight (or on device)

[JuLink]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

Using match to generate provisioning profile on a brand project leads to installation failure when deploying on device.

Command executed

match(
      type: development,
      team_id: RELEASE_TEAM_ID,
      app_identifier: NEW_BUNDLE_IDENTIFIER,
      readonly: false,
)
match(
      type: appstore,
      team_id: RELEASE_TEAM_ID,
      app_identifier: NEW_BUNDLE_IDENTIFIER,
      readonly: false,
)

This commands succeed without any issue. But using the generated provisioning profiles in Xcode Signing tabs leads to an error when releasing the application on TestFlight or when deploying the release version on a device.

The error when running a release build on device is:

Failed to install embedded profile for <NEW_BUNDLE_IDENTIFIER> : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.)

This error occurs even on a fresh new project using the base Xcode template and only changing the provisioning profiles to the one generated via match.

Environment

✅ fastlane environment ✅

Stack

Key	Value
OS	14.4.1
Ruby	3.0.6
Bundler?	true
Git	git version 2.44.0
Installation Source	~/.rbenv/versions/3.0.6/bin/fastlane
Host	macOS 14.4.1 (23E224)
Ruby Lib Dir	~/.rbenv/versions/3.0.6/lib
OpenSSL Version	OpenSSL 1.1.1w 11 Sep 2023
Is contained	false
Is homebrew	false
Is installed via Fabric.app	false
Xcode Path	/Applications/Xcode.app/Contents/Developer/
Xcode Version	15.3
Swift Version	5.10

System Locale

Variable	Value
LANG	en_US.UTF-8	✅
LC_ALL	en_US.UTF-8	✅
LANGUAGE

fastlane gems

Gem	Version	Update-Status
fastlane	2.220.0	✅ Up-To-Date

[JuLink]

It seems to work properly this week... I don't know what was going on...