Expo runs on android, ios, and the web. It is mention in the release notes i guess. It's not stupid, they changed the api, should have a deprecation warning and support the initial way of their export.
javascript ExpoMetroConfig.loadAsync is not a function when i run
I don't know what might be causing it.
That's understandable, it can take some.
Check to see if you have any changes or errors in your babel configuration. My app uses crna and expo, and my issue is that the font.loadasync() asynchronous function can't locate a.otf font file in the assets/fonts/ folder in my project. I didn't have this issue before. In some rare cases, this issue could be caused by incompatibility between the metro javascript minifier.
Fontfamily bold is not a system font and has not been loaded through font.loadasync.

