`bundle` ignores path alias if ran from `./ios` folder

[sidferreira]

I just finished updating to rn 0.63.2, but since that, our builds for release fails.
After a lot of digging, I found out that the problem is related to the bundle failing to resolve the path aliases if it is running from the ios folder.
This happens because we use Fastlane to assist the releases.

I tried both node ... bundle and npx ... bundle with the same results (running from command line).

(still digging for more details, but feels like a regression)

adding cd .. and cd ios on Bundle React Native code and images step fixes the issue, but it isn't the optimal solution...

[sidferreira]

So far, the only thing I managed to pinpoint is that at metro/src/DeltaBundler/traverseDependencies.js: resolveDependencies the aliased path is already resolved then running on the project root, but not when running from ios folder.

The problem seems to be inside the options.transform function used on metro/src/DeltaBundler/traverseDependencies.js:_processModule

[ajp8164]

As I understand, changes to the rn 0.63.2 (at least) include removing the use of PROJECT_ROOT and defaulting to PWD. It seems that cli is supposed to traverse up the dir tree until it finds package.json and set that directory. Seems this traversal is not working? See Allow changing the project path in react-native-xcode.sh

I followed the example in the above PR by adding export PROJECT_ROOT=$PWD/.. to the build phase script.

UPDATE:

This "work around" actually does not work. Changing the directory at https://github.com/facebook/react-native/blob/v0.63.2/scripts/react-native-xcode.sh#L69 breaks the ability to determine the path to the CLI based on https://github.com/facebook/react-native/blob/v0.63.2/scripts/react-native-xcode.sh#L106.

I hacked the script just to get it working.

There must be something else going on here - seems like a lot of people would encounter this issue..

[thymikee]

@grabbou can you weigh in?

[github-actions]

There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.