Provisioning profile has platforms "visionOS, watchOS, and iOS", which does not match the current platform "tvOS".

[Trevato]

Build/Submit details page URL

https://expo.dev/accounts/trevato/projects/tv-cook/builds/4cc0b723-1c85-4662-94e6-8d15947cffc0

Summary

I am attempting to build the tvOS demo and get a build to Testflight so I can install it on my Apple TV but it doesn't look like eas made a provisioning profile that enables the platform. I made a new one with tvOS enabled but I can't find a way to tell eas to use it.

Also mentioned in 1349.

eas version: eas-cli/14.2.0 darwin-arm64 node-v18.20.4

Managed or bare?

managed

### Environment

  expo-env-info 1.2.1 environment info:
    System:
      OS: macOS 15.2
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 18.20.4 - ~/.nvm/versions/node/v18.20.4/bin/node
      npm: 10.7.0 - ~/.nvm/versions/node/v18.20.4/bin/npm
      Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.15.2 - /Users/trevato/.gem/ruby/3.3.4/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.0, iOS 18.0, macOS 15.0, tvOS 18.0, visionOS 2.0, watchOS 11.0
    IDEs:
      Android Studio: 2024.1 AI-241.15989.150.2411.11948838
      Xcode: 16.0/16A5211f - /usr/bin/xcodebuild
    npmPackages:
      expo: ^52.0.16 => 52.0.23
      expo-router: ~4.0.9 => 4.0.15
      react: 18.3.1 => 18.3.1
      react-dom: 18.3.1 => 18.3.1
      react-native-tvos:  0.76.3-0
      react-native-web: ~0.19.10 => 0.19.13
    npmGlobalPackages:
      eas-cli: 14.2.0
    Expo Workflow: managed

Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check.
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check npm/ yarn versions
✔ Check for issues with Metro config
✔ Validate packages against React Native Directory package metadata
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

bunx create-expo-app tv-app -e with-router-tv
eas build --profile preview_tv

[douglowder]

If the tvOS build is going to use the same bundle identifier, then you will have to do the build with local credentials. EAS only seems to allow one provisioning profile for a given bundle identifier. I hit this problem with my own app.

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[douglowder]

I've marked this issue as accepted, and marked it as a gap in our documentation for EAS build that we will work on.

[Trevato]

The docs link appears to be what I was looking for. Thanks @douglowder!

Docs are easy. Please let me know if this is a place I can contribute.