Hi, Brent. We have one codebase that produces several different apps and uses a different Expo project for each app. For some of these apps, we have a separate staging build configured which points to our staging server environment (and is helpfully identified by a distinct app icon), each of which uses a different Expo project. My understanding is that this is one of the purposes of dynamic configuration, along the lines of the ability to “swap out configuration entirely in order to white label an app” as described in the documentation.
For each of these configuration sets, we must now store the EAS project ID. This certainly isn’t difficult, but it seems wrong - because each configuration already identifies itself uniquely by its slug. When I add the UUID for an EAS project, I’m either adding an extraneous specification (if the identifiers match up), or I’m introducing an inconsistent configuration (if they don’t).