Duplicate <targetName>Clip schemes after running prebuild

[ubufox]

Is it expected behavior to have additional Clip schemes after running npx expo prebuild?

When I make changes to the react-native-app-clip configuration values in my app.json, I sometimes forget to delete the ios directory before running npx expo prebuild. This leaves me with additional Clip options to choose from when I run npx expo run:ios --scheme. The order of the schemes doesn't seem to be consistent, and only one of the Clip options will work.

The failing options will throw an 'RCTAppDelegate.h' file not found error.

It's not a huge issue, but if you have any ideas for a direction to start looking, I'd love to submit a fix!

[nathan-ahn]

Strange bug! I don't have any initial hunches on what could be going wrong here. I don't see any reason for multiple schemes to ever be created.

If you have time to investigate and resolve, I'd be happy to take a look at a PR! Sorry I can't be of any more help with initial leads.

[ubufox]

It appears to be related to
apache/cordova-node-xcode#110

The add methods on the Xcode project object don't check if the app clip configurations have already been added to the project.pbxproj file, so each time I run prebuild, the react-native-app-clip plugin adds additional targets, build phases, etc.

I'll continue looking into it to see if there is an elegant way to overwrite the existing values.

I'm also new to Expo, and I could just be doing things incorrectly on my end.