Kudo Chien

would be good to see the details in the "Hide N more frames". or if you could share the raw crash log, it will be even better.

hi there! thanks for reporting the issue. i'm sorry that we introduced this regression when introducing new features. the issue is actually resolved by newer versions (still in alpha). given...

hi there! i tried your repro but it doesn't show the require cycle error for me. ```sh $ git clone https://github.com/hdwatts/expo-recreation-playground.git $ cd expo-recreation-playground $ git checkout require-cycle-example $ bun...

i can confirm the issue and accept the issue. also, let us keep it as lower priority. the error seems to be coming from the api-routes server renderer that we...

hi there! okhttp (the underlying network library of react-native android) supports transparent gzip. if you don't explicitly add the `Accept-Encoding`, it will gzip actually and network inspector would be correct....

> rewrite our existing splash-screen implementation to use a new API. We have to do it anyway to fully support Android 12. on android, if that's not a regression from...

going to merge this directly for the new expo-go to fix the high rate crash. let me know if there's any concern from post-review.

github actions ci keeps oom on building android versioned expo-go 🤦‍♂️

i had been thinking to remove the legacy code before react-native prefab support at some point. it's a good time. let me kick a ci instrumentation ci to make sure...

> https://github.com/expo/expo/actions/runs/5476977931 it breaks unfortunately https://github.com/expo/expo/actions/runs/5476977931/jobs/9975327136 alternatively, how do you think if we move the expo-modules-core androidTest from expo-go to bare-expo?