We’ve been attempting to upgrade from Expo 33 to 34. Since the update we have been getting the error fontFamily "FontAwesome" is not a system font and has not been loaded through Font.loadAsync.
We have been using FontAwesome like the docs suggest import { FontAwesome } from '@expo/vector-icons'; Has anything changed in SDK 34 in regards to this?
Interestingly, running expo init and selecting the tabs managed workflow, gives a boilerplate project that errors out with the pretty much the same error.
But around the space-mono font not being loaded through loadAsync, despite the fact that it is as part of loadResourcesAsync() of App.js.
Rolling back to expo 33 fixes the issue in either case.
I had the same issue I solved it updating versions in package.json, when you do a “expo start” appears some warning messages? because I need to update for example “expo-font” to “^6.0.1” I make these changes:
Also suffering the same problem. New app from scratch using SDK34. When using the simulator and device within Expo all icons show.
When i build for IOS and bundle app for my phone to test in testflight all icons give me the square box and question mark. Im using @expo/vector-icons i have cleared my node_module and re Yarn’d then published and OTA the app still the same. Haven’t resubmitted a new build yet, will try that later.
Thanks for all the replies! Had the same issue as well, while I had all the versions stated in this thread. I also had to remove the package-lock.json and then npm install again to get it working.
I’m still running into issues with this even after nuking everything and updating expo and expo-fonts to the recommended versions above. My package.json has the following dependencies:
i solved the issue, the problem is @expo/vector-icons change their font path.
Ionicons: require(’@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Ionicons.ttf’).
But i found some icon is like missing, example is MaterialCommunityIcons security-lock
i change to MaterialCommunityIcons security is exist.
After removing node modules, package-locks and reinstall all dependencies, I am still seeing this issue, but it only happens when I use expo build:android. Everything works fine when I use expo run
After removing iOS simulator from my Mac and redo “expo start”, it fixed.
Your iOS simulator is located something like this path
Users > [YOURUSERNAME] > Library > Developer > CoreSimulator > Devices > [devide ID].
We are experiencing the same issue. @expo/vector-icons does not work on Android in standalone app. It shows X box instead of an icon for FontAwesome.
It works fine in a simulator, but not when it is an apk file or published to google play store.
Figured it out and fixed the issue by updating SDK to 34.0.0. The Expo version was 34, however we were still referencing SDK 33.0.0, but after changing to SDK 34, the issue was solved.