"Unable to create cache directory for remote fonts" on Android (Expo), V2 Paywall

Hey ​@jice-lavocat,

Thank you for the post. This is Matt from RevenueCat, and I’d love to help with this.

I’m very sorry if any of the documentation is out of date. I’ll explore the font documentation to get this updated and make sure it only shows the correct information.

As you mention, this does sound like it is caused by memory issues. Emulators can be configured to have low memory to test edge cases, which could result in this issue. There are no additional Android permissions required for this, so it shouldn’t be related to any permissions that need to be granted in your app.

This could, in theory, happen on a real device if the memory is critically low. I’ll also raise this with the paywall team so we can explore whether this is something that could be improved.

Have you seen this happening on a real device? Do you have any crash logs in your app that show this happening in production? I asked the paywall team here, and we don’t have any known issues with fonts causing this type of crash that we’re aware of, but we will continue to monitor the logs.

If you wanted to avoid this step entirely, you can still host your fonts locally, which would avoid the need for this cache to be created. The fonts shouldn’t be downloaded if they are available locally. More information on this can be found here: https://www.revenuecat.com/docs/tools/paywalls/displaying-paywalls#custom-fonts

I hope this helps. If you have any other questions, or if there’s anything else I can help with, please don’t hesitate to reach out.

Thanks!