Best practice for EAS build with alternate bundle identifiers (bare workflow)

Expo Application Services (EAS)
5

Thanks for that. I seem to have gotten past that error by manually adding all of the targets to the TargetAttributes section of project.pbxproj:

TargetAttributes = {
					13B07F861A680F5B00A75B9A = {
						LastSwiftMigration = 1120;
					};
					ABF986F3273CBF0900BA7963 = {
						LastSwiftMigration = 1120;
					};
					ABF9870F273CBF1500BA7963 = {
						LastSwiftMigration = 1120;
					};
					ABF9878D273D3FF600BA7963 = {
						LastSwiftMigration = 1120;
					};
				};

Next I was getting ** ARCHIVE FAILED ** in the FastLane build. The original “Dev” target worked. This lead me to see that pods were not being created, so I modified the podfile to have a section for each target (as far as I can see, nothing in Xcode would do this automatically). Now the iOS build process seems to be working. :blush:

Now I am working on doing the same with Android. I have setup 3 productFlavor’s with 3 different applicationId’s. This is working locally. To get EAS Build to do this, it sounds like I need to override the gradleCommand (as shown here: Adding multiple targets and product flavors - #10 by wodin).

Would that just be :app:assembleStageRelease, for example? I will give it a try…