OTS parsing error about unicons HOT 23 CLOSED

I also have this problem in unicons 4.0.0
I decided to swap version 4 for version 3.
It works well for me:
<link rel="stylesheet" href="https://unicons.iconscout.com/release/v3.0.0/css/line.css">

from unicons.

Same problem

Edit: using v3.0.1 fixed but I dont know what icons I will lose

from unicons.

Fixed this issue in the latest patch
please use the latest version 4.0.8 and that will solve this issue.

The actual PR of the fix is #176 which is released with v4.0.8

from unicons.

nope... still there

from unicons.

Same problem - I'm using v4.0.0

from unicons.

Any way we can fix this? If you point us in the right direction, we might be able to contribute and fix it ourselves and open a PR for it @tarunmangukiya

from unicons.

hey 7aklhz, any luck with this issue?

from unicons.

thanks. console is just full of warnings. using v3.0.1 for now

from unicons.

Hello. Getting the same in Nuxt and using the URL mentioned on the website:

from unicons.

same problem using integration code recomended by website with vue.

i use <link rel="stylesheet" href="https://unicons.iconscout.com/release/v4.0.0/css/line.css"> in my index.html

from unicons.

Same problem

from unicons.

Same problem

from unicons.

Same problem!

from unicons.

same problem v4.0.0

from unicons.

@tarunmangukiya: any news on this please ?

from unicons.

Same problem here.

from unicons.

Any chance of a fix? Sure, it's not urgent, but because it fills up the console with warnings it makes it easy to miss other warnings.

from unicons.

Still an issue! Please fix

from unicons.

I’m having the exact same issue with 4.0.1. I’m referencing the CSS and font files locally, but I know the paths and everything are correct because the icons display correctly, yet I get the “OTS parsing error” for all .woff2 fonts.

from unicons.

Same problem. v4.0.0 line
Chrome: " Failed to decode downloaded font: "
Mozilla: "downloadable font: rejected by sanitizer "

from unicons.

any solution?

from unicons.

has anyone fixed this yet without downgrading the version

from unicons.

@tarunmangukiya Any news regarding this issue?

from unicons.