Both "expo prebuild" and "expo run:android" commands fail due to invalid URL string

[elektromob]

Both "expo prebuild" and "expo run:android" commands fail due to invalid URL string

[byCedric]

Forwarded this issue npm/cli#7537, I'll also backport & release the fix ASAP.

If others are running into this as well, the fastest fix for now is to downgrade npm from 10.8.0 (current latest) to 10.7.0. That would avoid this issue for now, until we released a workaround, or npm has released a fix.

You can do that with npm install --global [email protected], or npm i -g [email protected]

[byCedric]

Heads up, [email protected] will likely (not released yet) ship with a fix. See npm/cli#7537

For now, only SDK 51 has been patched. We will likely hold off on backporting this to older versions, as npm seems to fix it soon-ish.

[elektromob]

@byCedric I would like to add that running npx expo prebuild --template https://github.com/expo/expo/tree/main/templates/expo-template-bare-minimum only once makes all further npx expo prebuild and npx expo run:android commands work without a problem.

I would also like to add that the same problem happens when npx eas-cli build --local --platform android --profile $PROFILE is invoked as well, where $PROFILE is either preview or development. This wasn't specified in the initial body of the issue, so I apologize.

[byCedric]

Yep, I just found the issue @elektromob. It's npm 10.8.0 returning a different response than npm <10.7.0. (Note the missing quotes)

[elektromob]

Update

Following is a temporary fix:

npx expo prebuild --template https://github.com/expo/expo/tree/main/templates/expo-template-bare-minimum

[byCedric]

Hi @elektromob, thanks for the report. It's interesting what's going on here, my best guess is that either Linux or npm decided to change its output. Basically, how this works is that it should be parsing the string, with the quotes. Meaning that it's technically just a valid JSON string, e.g.

But, we can make that less brittle.

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.