We have an internal header called Swift.h used as a wrapper import. Due to it being project level (aka internal), it was thought the generic file name would not cause issues, but due to the way Expo does builds, it conflicts with their own Swift.h header.
This change renames that internal header and updates all imports statements.
Testing Plan
[x] Was this tested locally? If not, explain why.
Tested local build in Xcode
Manually updated Expo test app dependency to use this change and confirmed successful build and run npx expo run:ios
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)
Summary
We have an internal header called
Swift.h
used as a wrapper import. Due to it being project level (aka internal), it was thought the generic file name would not cause issues, but due to the way Expo does builds, it conflicts with their ownSwift.h
header.This change renames that internal header and updates all imports statements.
Testing Plan
Manually updated Expo test app dependency to use this change and confirmed successful build and run
npx expo run:ios
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)