Hyo

This has been covered in the recent version. Try `3.5.1` and comeback.

@erikAlon is right. There is no `--boilerplate` today. The doc should be updated.

@kayhadrin @jrwats May we get any clue on this? We can't apply react-native 0.68, the new architecture because of this issue.

This is not restricted to expo SDK 45. Below projects also occurs the same error. ``` npx react-native init Puzz --template react-native-template-typescript yarn add babel-plugin-fbt babel-plugin-fbt-runtime fbt react-native-fbt '@fbtjs/default-collection-transform' yarn...

@kayhadrin Thanks so much for the response. Desperately waiting for this. I am not capable with new architecture yet.

People who might face the same issue can try install package from https://github.com/hyochan/react-native-fbt as a workaround.

If the user wants to refresh data, it should force to get recent data to the user, not from the caches. The subscription design with the caches and updating is...

Yes it looks like you can try to integrate the `resolver` in client side and test it out!

Great idea! I think this can be provided with sqlite. https://docs.expo.dev/versions/latest/sdk/sqlite/

Oh `SQLite` does not work on `web` 😞 You can still use `AsyncStorage` but thinking on the issue again, I don't think we need storage for this. How about just...