Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Font failures on clean install #19

Open
4 tasks done
joshforman opened this issue Mar 17, 2023 · 1 comment
Open
4 tasks done

Font failures on clean install #19

joshforman opened this issue Mar 17, 2023 · 1 comment

Comments

@joshforman
Copy link

Prerequisites

Please answer the following questions for yourself before submitting an issue.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed
  • I'm reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior

Upon first load after compiling with expo start, the app loads without errors

Current Behavior

The app loads with question marks in place of icons, and I see a bunch of console errors like this:

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

  • If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

  • If this is a custom font, be sure to load it with Font.loadAsync.
    at node_modules/expo/node_modules/expo-font/build/Font.js:27:29 in processFontFamily
    at node_modules/react/cjs/react.development.js:365:30 in Component.prototype.setState
    at node_modules/@expo/vector-icons/build/createIconSet.js:23:50 in Icon#componentDidMount

  • ... 7 more stack frames from framework internals

Failure Information (for bugs)

See above

Steps to Reproduce

expo start from clean install

note that the current version of expo go is incompatible with the expo version in the current base repo, so I updated the version of expo in the base repo. There were also dependency conflicts that required that I install with npm install --legacy-peer-deps.

Context

I am running the most recent version of expo/expo go on a Ventura Mac M1.

Failure Logs

See above

@joshforman
Copy link
Author

The root problem here is Expo Go requiring a more recent version of expo than is in this repo. But updating expo created a bit of a dependency cascade and got us to a place where AppLoading breaks.

It took a day, but I replaced AppLoading with SplashScreen (this part was easy) and tweaked package versions so that they all managed to play nicely with each other (this part was hard). See the attached updated App.js and package.json, which now loads without errors. There are some minor issues in image size rendering, but this is progress.

updated_expo.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant