Failed to decode downloaded font in android app

There are various font files, all from the same family. I am trying to load them all. The font files are. I am loading them from a local folder, and there are various font-files, like Lato-Black.

In the css rule you have to add the extension of the file. This example with the deepest support possible:. Sometimes this problem is caused by the font itself. Google font provides the correct font you need but if font face is necessary i use Transfonter to generate all font format. Sometimes is the FTP client that corrupt the file not in this case because is on local pc. I experienced a similar issue in Visual Studio, which was being caused by an incorrect url path to the font in question.

You can also check this out for extending the mime. For me, this error was occuring when I referenced a google font using https. When I switched to http, the error went away. Depending on your mood, it may feel counterintuitive, lol. If you ftp your files with an 'auto' method, and you get this error message, try ftp forcing the binary method. This are the warnings that come up in the Chrome developer console:.

Intuiton tells me that there is something wrong with webpack. So here is the webpack. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Failed to decode downloaded font on lambda production app Ask Question. Asked 2 years ago. Active 2 years ago. Viewed times. You should have something close to this in your. My two cents: I was able to solve the issue importing the fonts from the index.

I encoded the font with base64 locally. I am using the Nucleo app to do that by way. Skip to content. Star New issue. Jump to bottom. Copy link. Description Since v0. I was on 0. I was getting a warning in Chrome only. Depending on your mood, it may feel counterintuitive, lol. In my case it was caused with an incorrect path file, in. For me, this error was occuring when I referenced a google font using https. When I switched to http, the error went away. In my case, this was caused by creating a SVN patch file that encompassed the addition of the font files.

Like so:. The solution was to upload the font files directly into the branch from my local file system. You can test for this by uploading other types of binary data like images.