#eva_error

1 messages ยท Page 1 of 1 (latest)

slender skyBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1508789512548126830

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

cloud quartz
#

Sorry for no response last time - forgot I muted the server ๐Ÿ˜…

full root
#

๐Ÿ‘‹ No worries.

#

I've just checked your last thread, what is your follow up qestion ?

cloud quartz
#

It hasn't been resolved since, at least judging from stripe-react-native changelogs

full root
cloud quartz
#

"closing this, contact discord server" thinkies

#

and "just install react-native-webview" which I would like to avoid, it's claimed to be an optional peer dependency

#

Just tried 0.66.0 - same issue. Caches were obviously reset

full root
full root
#

I'm not able to, can you describe the reproduction steps exactly ?

slender skyBOT
cloud quartz
#

I'm not sure what specifically reproduces it in our case, if I had to guess it'd be @rnx-kit/metro-resolver-symlinks@0.2.2 - a specific resolver version that does not rely on internal metro's symlink resolver and resolves correct react version in mobile's project context rather than picking up other project's one (pnpm non-hoisted monorepo)

wraith bobcat
#

๐Ÿ‘‹ Hey, taking over here, just catching up

cloud quartz
#

Nevermind I might've found the cause

#

Someone pinned our metro version to 0.76 in root package.json (us being on 0.83) pepeweird

wraith bobcat
#

Ah, I see!

cloud quartz
#

Yep seems to working so far, sorry for the confusion, we can probably close this. I'll leave the comment on the issue in case it helps someone in the future too