Can't use loaded fonts as per documentation
See original GitHub issueFollowing the Using Custom Fonts guide to load a custom font and then using fontFamily: 'my-font-name'
in a StyleSheet
always results in the following error message:
fontFamily ‘my-font-name’ is not a system font and has not been loaded through Exponent.Font.loadAsync.
However, if I use fontFamily: Font.style('my-font-name').fontFamily
it works correctly. I’m not sure if this means the documentation is incorrect (maybe a breaking change was introduced recently?) or if this is some sort of bug.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
The Best Font Loading Strategies and How to Execute Them
Zach Leatherman wrote up a comprehensive list of font loading strategies that have been widely shared in the web development field.
Read more >Best practices for fonts - web.dev
Be cautious when using preload to load fonts # Inlining font declarations and adjusting stylesheets may be a more effective approach. These ...
Read more >Solved: Reader doesn't recognize installed font - 9896699
Please navigate to Adobe Reader's Preferences from Edit>Preferences>Page Display>Select "Use Local Fonts">Click OK>Close the PDF and Adobe Reader.
Read more >How to use web fonts in CSS - LogRocket Blog
Designers recommend using fonts sparingly, with just one or two typefaces per document; Custom fonts typically require a few hundred KB.
Read more >how do I add new fonts to Adobe Acrobat Pro DC??
If you're trying to repair a document from someone else, that uses a given font and you can't find it via DC for...
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
One thing that might help is in old versions of the documentation there should be a big warning banner at the top that says something about this version being outdated. Might cause people to look twice at the documentation version
Hi All,
I’m having the same problem. Lost tow hours on this. Here is my code. Any idea?
And My package.json