React Native: "ownKeys target is non-extensible but key is missing from trap result" when calling Object.entries

[ganselu]

When calling Object.entries / .keys / .values on a store entry with only primitives an exception is thrown
"ownKeys target is non-extensible but key is missing from trap result"
Issue only reproducible on Native Devices (Tested on Android and iOS)

Example:
https://snack.expo.dev/fyFeNWh0tFKuA5eA0rlCM

[dai-shi]

Thanks for reporting. Is this latest RN?
Can someone reproduce the same error without Valtio? (Just using Proxy and Reflect.)

[ganselu]

Thanks for the quick response.
RN-Version: 0.73.6

[ignaciosantise]

Hey @dai-shi 👋 were you able to find the cause of this issue?

[dai-shi]

Unfortunately not. We need someone to help dig into it.

[enzomanuelmangano]

@dai-shi I'm able to reproduce the issue with the latest version of React Native and Expo. Actually, the issue happens also after trying to console log the state.

The issue is caused by the "configurable" option in the createSnapshotDefault function:

const desc: PropertyDescriptor = {
  value,
  enumerable: enumerable as boolean,
  // This is intentional to avoid copying with proxy-compare.
  // It's still non-writable, so it avoids assigning a value.
  configurable: true, // This option is causing the crash on RN 
}

Although I have no idea why

[dai-shi]

Hi, thanks for investigating it.
In that case, I think you can reproduce the issue without Valtio easily.
Can you report it to RN repo and see if this change and the crash is intentional?

[tolypash]

Hey guys, any updates on this one? Happens with latest version of Valtio. Not on 1.10.5 though.

[dai-shi]

Just to confirm, does it reproduce with the latest version of v1 too, right?

I would need someone to help reproducing it without Valtio.

[overthemike]

I wonder if the fix in #988 could have fixed this as well?

[dai-shi]

ownKeys is used in vanilla.ts.

[k33lil]

Is there any help on this or workaround?

I tried even with v1, the same issue

[k33lil]

v1.6.3 is working fine, i tested with the latest react native version

[dai-shi]

#874 (comment)

I think it's an issue even without Valtio. Can anyone help?

[overthemike]

https://snack.expo.dev/@overthemike/valtio-test

I'm not sure if this is what you're looking for or not. It seems to work ok with the proxy object as well as the simple copy function that emulates snapshots.

[dai-shi]

Can someone reproduce the same error without Valtio? (Just using Proxy and Reflect.)

My intention was to reproduce the error without Valtio and reports to RN team to see if it's intentional.