ReferenceError: Property 'SkiaApi' doesn't exist, js engine: hermes

[bj97301]

Description

I get this randomly when saving and auto-refreshing in expo 49 with ios. android seems to work fine.

Version

1.0.4

Steps to reproduce

hit save on a js file then wait for the app to reload.

expected: no error

actual: ReferenceError: Property 'SkiaApi' doesn't exist, js engine: hermes

Snack, code example, screenshot, or link to a repository

should be happening to most people's projects. If not ill whip up a snack.

[jackculprit]

I'm using a bare react native app, and this is happening to me too.

"react-native": "0.72.6",
"react": "18.2.0",
"@shopify/react-native-skia": "^0.1.230",

[PierreAndreis]

in my case it shows up after my app tries to recover from an error boundary. reloading the app fixes it.

[christophemenager]

Same for me!

[SerranoPablo]

same

[xb1g]

I changed from bun to yarn and it's gone.

[bj97301]

I use yarn and still get the error

…

On Thu, Jan 18, 2024 at 4:41 AM Bunyasit Fang ***@***.***> wrote: I changed from bun to yarn and it's gone. — Reply to this email directly, view it on GitHub <#2039 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALCDP54J4AT635LIPXLZB3YPEKBPAVCNFSM6AAAAABAN6AK32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGQYDQNZRG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bj97301]

This bug is super annoying. Is there any way I can help get this fixed?

[bj97301]

@wcandillon are you able to reproduce this issue?

[bj97301]

@chrfalch watcha thinkn? Can I help in any way?

[bj97301]

Does anyone on this thread have any tips on where I can start on fixing this?

[christophemenager]

I did not had this problem again, maybe because I upgraded to the latest version of skia and expo and reanimated? I am not sure why but I would try upgrading all libs involved first

[wcandillon]

@bj97301 please send us a small project where we can reproduce the issue.

[jackculprit]

It did eventually go away from me after updating tons of libs as well. Seems like the same happened for @christophemenager

[klcantrell]

I encountered this today after updating Expo from 50 to 51 and updating a few other dependencies as well. I could only surface the error twice or so (full reloading on iOS), and haven't been able to resurface it since. If I can reliably reproduce it, I'll try to distill and send a small reproduction repo.