Fingerprint: support projects with several Xcode targets / schemes

[andriyslyusar]

The CLI create/use the build cache without taking in account the Xcode schema.

Steps to reproduce:

• run npx rock run:ios --scheme com.app.bundleid1 would create the build cache rock-ios-simulator-Debug-63a0347ada830c67930f42896fd839c1c2186d4f
• runing npx rock run:ios --scheme com.app.bundleid2 would report Found build cache for: rock-ios-simulator-Debug-63a0347ada830c67930f42896fd839c1c2186d4f and skip building the --scheme com.app.bundleid2.

Expected behaviors:
The cache should take in account xcode schema when building and using cache.

[thymikee]

This is a valid point. To support it we'll need to consider whether to put scheme (and maybe target) in the artifact name as "traits" (internal naming) or in the fingerprint. Which brings me to potential breaking change: getting rid of simulator-Debug part entirely, as it could be just a part of fingerprint.

[andriyslyusar]

Does rock cli support alternative to "react-native run-ios --project-path ..."? The ideas is temporarily workaround the missing scheme support by creating the separate Xcode/Gradle projects in apps/app1, apps/app2, ... subfolders.

[thymikee]

Isn't that something you could achieve through platform configuration with sourceDir?

[mrjman]

This would be great to support as we currently have 5 schemes.

The workaround we are trying is loading our env file (.env.test, .env.qa, etc.) with dotenvx and then setting an env that can be used in the rock.config in the fingerprint -> env field.

In package.json

"scripts": {
  "ios:dev": "dotenvx run -f .env.development -- rock run:ios --scheme=AppDev",
  "ios:qa": "dotenvx run -f .env.qa -- rock run:ios --scheme=AppQa"
}

Within rock.config.mjs we are setting:

export default {
  fingerprint: {
    env: [process.env.APP_ENV]
  }
}