[match] Imported tvOS provisioning profile generated name does not match the one expected when retrieving profiles for building the tvOS app about fastlane HOT 2 OPEN

Hello, @aureliencolas ADPWorkforceNow

Thank you for providing the details about your issue with Fastlane and provisioning profiles for tvOS. Let’s troubleshoot this together!
It seems that the generated provisioning profile names are not matching the expected format, specifically missing the _tvOS suffix. Here are some steps to address this:

Specify the Platform Parameter:
When using Fastlane’s match for signing, make sure to explicitly specify the platform parameter as tvos.
For example:

match(platform: "tvos")

Check Repository Naming Conventions:
Ensure that your repository follows the correct naming conventions for tvOS provisioning profiles.
The expected format should include the _tvOS suffix (e.g., AppStore_lu._tvos.mobileprovision).
Verify Fastlane Version:
Make sure you’re using the latest version of Fastlane. Update it if necessary.
Sometimes updates include fixes for compatibility issues.
Review Your Fastlane Configuration:
Double-check your Fastlane configuration files (e.g., Fastfile, Matchfile) to ensure there are no conflicting settings or overrides.
Confirm that the correct provisioning profiles are being used.
Test with a Different Developer Account:
You mentioned that the issue occurs when importing profiles using match import.
Try using a different developer account (where you have admin access) to see if the behavior is consistent.
Inspect the Provisioning Profiles:
Manually inspect the provisioning profiles in your repository.
Verify that they indeed match the expected format and contain the necessary information for tvOS.

Remember, debugging these issues can be like untangling headphone cables—it takes patience!.

I hope this info is helpful to you.

Best Regard,

from fastlane.

Thanks @gregory109 for taking time to help me with this issue.

Regarding the steps you mentioned,

1. Specify the Platform Parameter
   I do use the platform parameter with tvos value as stated in my issue description:
   bundle exec fastlane match import --type appstore --skip_provisioning_profiles true --clone_branch_directly true --git_branch XXXXXXXX --team_id XXXXXXXX --app_identifier XXXXXXXX --platform tvos
   The issue does not occur when I create tvos provisioning profiles using match (from a lane this time) with the following command, it's just the import that fails to name provisioning profiles with the _tvos suffix:
   match(type: type, git_branch: team_id, team_id: team_id, app_identifier: ids, platform: "tvos", clone_branch_directly: true, verbose: match_verbose)
2. Check Repository Naming Conventions
   Yes, provisioning profiles created by match all have the _tvos suffix. I can create these profiles for all the developer accounts I'm an admin of. But for developer accounts I'm only granted the developer role, I have to import the provisioning profiles created by the admin but this is then that the issue occurs.
3. Verify Fastlane Version
   I use the latest version of fastlane but the issue still occurs.
4. Review Your Fastlane Configuration
   I use the match import command from the command line, not from a lane.
   In the Fastfile the only global setting set is default_platform(:ios) but I assume it is overridden by the platform parameter provided to the match import command.
   In the Matchfile, I only set the git_url, the storage_mode and the type (appstore).
   The provisioning profile imported to BitBucket is indeed the one I want to export, it's just the renaming that is wrong.
5. Test with a Different Developer Account
   I have not tested that yet but I'm afraid it won't change anything as there is nothing specific to the dev account I use when I experience the issue.
6. Inspect the Provisioning Profiles
   The provisioning profile provided by the developer account admin do have the platform: tvOS property and is a valid tvOS provisioning profile as, once I have renamed the one generated by match (adding the _tvos suffix) on BitBucket, everything works afterwards (ie. match retrieves the provisioning profile and then the app is built, uploaded and available on AppStoreConnect).

Would you be so kind as to try by yourself if you reproduce the issue by any chance?

Thanks again anyways.

from fastlane.