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

Android: Some .ttf fonts cause 'Layout -n < 0' Error #7301

jsncmgs1 opened this Issue Apr 29, 2016 · 5 comments


None yet
8 participants

jsncmgs1 commented Apr 29, 2016

For version 0.22.0, Android only, on a 2015 Macbook Pro:

I have some custom fonts in my application, OpenSans and FiraSans, both from Google Fonts as well as some variants, such as OpenSans-Light, FiraSans-Bold, etc. Everything works fine on iOS.

Android renders the OpenSans font's fine. When it tries render <Text> with FiraSans fontFamily, I get this error:
screen shot 2016-04-29 at 3 44 32 pm

If I remove the font from the app, the error goes away and it just uses the default, so I don't think it's a naming issue. I'm not really sure what to do with this error message. I tried changing font sizes, but no luck.


This comment has been minimized.

mmazzarolo commented Sep 15, 2016

Still having the same issue on react-native@0.33.
Does anyone have any tip on on this?


This comment has been minimized.

jleepeak commented Nov 15, 2016

Still having on react-native@0.37


This comment has been minimized.


hramos commented May 25, 2017

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.

@hramos hramos closed this May 25, 2017

@hramos hramos added the Icebox label May 26, 2017


This comment has been minimized.

Deviloppeur commented Feb 6, 2018

I had the same problem using this font (FiraSans). I used the official font ( and it worked. Hope that can help.


This comment has been minimized.

morfsys commented Jun 30, 2018

Same issue with Rubik font, please reopen

@facebook facebook locked as resolved and limited conversation to collaborators Jul 19, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.