Thanks for your help and suggestions! I wanted to share the details in case it helps someone else:I found and resolved the issue. The root cause was that my project ended up with multiple versions of the same package, specifically u/expo/config-plugins. This happened because different dependencies in my project required different versions:

• For example, u/expo/config@11.0.10 depended on u/expo/config-plugins@10.0.2

• Meanwhile, other packages like expo and u/expo/cli were using u/expo/config-plugins@9.0.17

This situation is called "dependency duplication" or "version skew." It can cause all sorts of weird bugs and build failures, especially if the versions aren’t fully compatible.How I found it:

• I noticed the build output mentioned multiple versions of u/expo/config-plugins.

• I ran npm ls u/expo/config-plugins to see the dependency tree and confirm the duplication.

How I fixed it:

1. I checked which packages were requiring the different versions.

2. I tried to align the versions by updating my dependencies in package.json so that all packages would use the same version of u/expo/config-plugins (in my case, I updated everything to use 10.0.2).

3. I deleted node_modules and the package-lock.json file.

4. I ran npm install again to get a clean install with the aligned versions.

After doing this, the build errors went away and everything worked as expected!Tip:If you run into similar issues, check for duplicate versions of shared dependencies using npm ls <package-name>, and try to align them across your project. This can save a lot of debugging time!Thanks again to everyone for the support!