TextInput on working with custom fonts

Hi @nandorojo, love the project – thanks for making this package available.

I’m experiencing issues when using custom fonts specifically when using the dripsy imported TextInput. All my other pages and Text items are using the custom font appropriately.

Have you experienced this or aware of what might be causing it? If I replace the dripsy TextInput with the standard react-native the error goes away.

Thanks!! Ben

AppEntry.bundle?plat…&minify=false:28030 fontFamily "NunitoSans" 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. 

[benjamin-r-erb]

@nandorojo Thanks again for following up on this. We made the changes you suggested in the loading to set the default weight to the generic font name ‘NunitoSans’ and that got rid of the error that was only appearing for us in the TextInput.

We also took a closer look at the new instructions. The font we are using has many different files for each style/weight, so the arial example with multiple weights per font name caused some confusion.

The other huge realization was that we had an unnecessary theme.text.body style element that was causing our font styling not to work unless using a text variant (which we had adopted as a workaround).

Thankfully everything is working now and we understand the process much better.

Thank you so much for your help and for making this awesome library available!

Best, Ben

[nandorojo]

Any update?