Building multiple standalones with different release channels for the same project?

Expo Development Tools
1

Hello,

We’re attempting to create several versions of our application binaries that point to different release channels for the same project. We would like to do this so that we can provide internal users with three separate standalone binaries for different environments, but also use publish:set to promote Javascript bundles through different release channels. For example:

  • Development
    • Environment: development
    • Application Name: App Dev
    • Icon File: ./icons/dev.png
    • Bundle Identifier: com.company.AppDev
    • Expo Project: "app"
    • Project URL: https://exp.host/@company/app?release-channel=dev
  • QA
    • Environment: qa
    • Application Name: App QA
    • Icon File: ./icons/qa.png
    • Bundle Identifier: com.company.AppQA
    • Expo Project: "app"
    • Project URL: https://exp.host/@company/app?release-channel=qa
  • Production
    • Environment: prod
    • Application Name: App
    • Icon File: ./icons/prod.png
    • Bundle Identifier: com.company.App
    • Expo Project: "app"
    • Project URL: https://exp.host/@company/app?release-channel=default

We are using turtle to build these, with appropriate app.json files having the attributes described above. However, it seems that turtle is pulling the application manifest based on the project, and not respecting the values found in the app.json file we’re providing. We’ve tried explicitly setting the --public-url to the full Expo project path and not including Expo credentials, but turtle is still overriding with the values from the manifest.

Is there any way to accomplish what we’re trying to do?

2

Does anyone have any advice?

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.