Icons are not rendering and receiving fontFamily errors after upgrading to Expo 35
See original GitHub issueIssue Description
I have upgraded my project to Expo 35, and immediately began seeing fontFamily errors like so:
fontFamily "FontAwesome5Free-Regular" is not a system font and has not been loaded through Font.loadAsync
I believe this is because Expo began splitting their monolith package into separate, use specific packages.
For example, these font packages are now imported as:
import { FontAwesome5, FontAwesome, Ionicons } from "expo-vector-icons";
or
import * as Font from "expo-font";
instead of being brought in with “Expo” itself.
I would assume this is a fairly straightforward fix, to begin using the new API to load fonts.
I see that there are instructions to use Font.loadAsync
with something like:
...Ionicons.font
but this also does not work.
Expected behaviour
Fonts load correctly, without error.
Actual behaviour
Fonts error out.
Steps to reproduce
Use Expo 35, and NativeBase ^2.12.0
My dependencies:
"dependencies": {
"@babel/plugin-transform-flow-strip-types": "^7.4.4",
"@blueprintjs/core": "^3.15.1",
"@types/react": "^16.8.14",
"@types/react-dom": "^16.8.4",
"antd": "^3.16.6",
"axios": "^0.18.0",
"babel-plugin-import": "^1.11.0",
"babel-plugin-module-resolver": "^3.2.0",
"babel-polyfill": "^6.26.0",
"base-64": "^0.1.0",
"expo": "^35.0.0",
"expo-analytics-segment": "~6.0.0",
"expo-calendar": "~6.0.0",
"expo-constants": "~6.0.0",
"expo-font": "~6.0.1",
"expo-keep-awake": "~6.0.0",
"expo-location": "~6.0.0",
"expo-permissions": "~6.0.0",
"expo-vector-icons": "^10.0.1",
"formik": "^1.5.8",
"humps": "^2.0.1",
"identity-obj-proxy": "^3.0.0",
"less": "^2.7.2",
"lodash": "^4.17.11",
"lodash.memoize": "^4.1.2",
"moment": "^2.24.0",
"native-base": "^2.12.1",
"parcel-bundler": "^1.12.3",
"prop-types": "^15.7.2",
"qs": "^6.8.0",
"react": "16.8.3",
"react-dom": "^16.8.6",
"react-formal": "^1.0.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz",
"react-native-autolink": "^1.8.1",
"react-native-calendars": "^1.210.0",
"react-native-easy-grid": "^0.2.1",
"react-native-gesture-handler": "~1.3.0",
"react-native-reanimated": "~1.1.0",
"react-native-segmented-control-tab": "^3.4.0",
"react-native-snap-carousel": "^3.8.0",
"react-native-storage": "^1.0.1",
"react-native-uuid": "^1.4.9",
"react-navigation": "^3.11.1",
"react-redux": "^7.1.0",
"react-router-dom": "^5.0.0",
"react-router-native": "^5.0.0",
"react-testing-library": "^7.0.1",
"redux-starter-kit": "^0.5.1",
"redux-test-utils": "^0.3.0",
"redux-thunk": "^2.3.0",
"sentry-expo": "~2.0.0",
"shared": "^0.2.0",
"utf8": "^3.0.0",
"uuid": "^3.3.3",
"yup": "^0.27.0"
},
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
Error with Expo fontFamily "material-community" is not a ...
I was able to solve this by deleting yarn.lock (I am using yarn) and removing node_modules after upgrade. Then running yarn install again....
Read more >Expo 34 Vector Icons not working
Since the update we have been getting the error fontFamily "FontAwesome" is not a system font and has not been loaded through Font....
Read more >material-icons - npm
Latest icon fonts and CSS for self-hosting material design icons. This package is automatically updated, so it will always have the latest icons...
Read more >Common Mistakes With Adding Custom Fonts to Your iOS App
It's pretty easy to add your own fonts in your iOS app but there are some common pitfalls to watch out for. Let...
Read more >expo unrecognized font family - You.com | The AI Search ...
Minimal reproducible example · Initialize new project the latest versions · downgrade expo · installing react-native-vector-icons · tried installing react-native ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was seeing the same error (for both fonts and icons) when upgrading to Expo SDK35 (didn’t happen when upgrading previous SDK upgrades). I was able to fix it in my environment by doing the following:
Then:
I am not sure exactly where the conflict was but the above worked for me. It seems others are experiencing something similar Expo Issue #5717 - Unrecognized font family on SDK35 and a few in the Expo issue mention NativeBase.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.