expo: [iOS 16.4 + JSC]: Unable to resolve [package] from [dependency/file/path]

I’m also using Hermes and running into the same issues but only with Expo and not in a bare React native project @mypalvikram @brentvatne

In the repo I originally linked I included a branch that is using the 48 version of Expo (hermes support) and get all the same errors: https://github.com/billyjacoby/expo-unable-to-resolve/blob/updated-expo-cli/package.json

thanks @IlyaSemenov! the workaround suggested by @robhogan in https://github.com/facebook/react-native/issues/36794#issuecomment-1500880284 will work, with a slight tweak to extend the default expo metro config:

const { getDefaultConfig } = require('expo/metro-config');

const config = getDefaultConfig(__dirname);
config.server.rewriteRequestUrl = (url) => {
  if (!url.endsWith('.bundle')) {
    return url;
  }
  // https://github.com/facebook/react-native/issues/36794
  // JavaScriptCore strips query strings, so try to re-add them with a best guess.
  return url + '?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true';
};

module.exports = config;

alternatively, switching to hermes will resolve this and is a good choice! it is the default in sdk 48 and we recommend it.

This is probably caused by the recent problem in iOS 16.4: https://github.com/facebook/react-native/issues/36794

@brentvatne You may want to consider to reopen the issue as it’s a valid problem confirmed by RN upstream. Expo may want to have its own suggested workaround.

any fix? it’s been 4 months…

@mypalvikram - the react-native team is working on a fix: https://github.com/facebook/react-native/issues/36794#issuecomment-1519544863

however, i personally would recommend that you use this as one more piece of motivation to switch from jsc to hermes. that will also resolve the issue and bring many other benefits, such as an improved debugging experience

I’m actually using Expo version 48 and Hermes is default but, I still run into this. This makes me think that there’s potentially another package causing this issue in my case. Thanks for the feedback, I’ll dig a little more.

I added that code in my expo metro config but I still get the same error. Fair enough, the app takes longer before crashing, but it still does.

Here is my metro.config.js file. Is there anything I’m doing wrong?

const { getDefaultConfig } = require("metro-config")
const { getDefaultConfig: getDefaultExpoConfig } = require("@expo/metro-config")

let metroConfig
let isExpo = false
try {
  const Constants = require("expo-constants")
  // True if the app is running in an `expo build` app or if it's running in Expo Go.
  
  isExpo =
    Constants.executionEnvironment === "standalone" ||
    Constants.executionEnvironment === "storeClient"
} catch { }

if (isExpo) {

  metroConfig = getDefaultExpoConfig(__dirname)

  metroConfig.resolver.assetExts.push('cjs');

  // START: This is a workaround for an upstream bug in react-native

  metroConfig.server.rewriteRequestUrl = (url) => {
    if (!url.endsWith('.bundle')) {
      return url;
    }
    // https://github.com/facebook/react-native/issues/36794
    // JavaScriptCore strips query strings, so try to re-add them with a best guess.
    return url + '?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true';
  };
  
  // END
  
} else {
  
  const { makeMetroConfig } = require("@rnx-kit/metro-config")
  const MetroSymlinksResolver = require("@rnx-kit/metro-resolver-symlinks")

  metroConfig = (async () => {
    const defaultConfig = await getDefaultConfig()
    return makeMetroConfig({
      projectRoot: __dirname,
      
      // watchFolders: [`${__dirname}/../..`], // for monorepos
      resolver: {
      
        resolveRequest: MetroSymlinksResolver(),

        assetExts: [...defaultConfig.resolver.assetExts, "bin", "cjs"],
      },
      })
  })()

}

module.exports = metroConfig