Georg von der Howen

@MoElnaggar14: As @MatrixSenpai said: Your patch might fix the issue with parsing the metadata. But **it does not help to render the duotone icons** correctly! I agree with @MatrixSenpai that...

Wow, if we can do this with ligatures instead of SVG, this would be great. Re. new repo: Ideally we could do an in place update, so people would not...

I downloaded https://github.com/thii/FontAwesome.swift/pull/245 and tried to test it with duotone icons, but the demo app for iOS crashes in `FontAwesome.swift:331` with the following error: `Optional(Swift.Unmanaged(_value: Error Domain=com.apple.CoreText.CTFontManagerErrorDomain Code=105 \"Could not...

To implement FA Pro support, follow the instructions from @pgrundner. To get **all** FA Pro icons, you need to hack a bit by following this: https://github.com/thii/FontAwesome.swift/issues/230#issuecomment-605018622.

@austintt It would help troubleshooting if you can catch the value of `style.fontName()` in the debugger. Then we would know which `fontName` is causing the problems. A potential cause for...

@austintt When you added the font files to the project, did you check the "Copy if needed" option? Also make sure that the all font files have the correct target...

@mralexhay You should probably check with @austintt if https://github.com/thii/FontAwesome.swift/issues/232#issuecomment-609626259 did the trick for him. My bet is still that the fonts were not added to the target of the app.

@morganchen12 Any idea what is happening here? This is still current with the latest SDK. Thanks for checking!

No need to stack trace IMHO. The crash occurs if the email address used for sign in with email does not match the email address of the currently logged in...

@morganchen12 And yes, it is consistently reproducible. Take any user on a device and log the user into Firebase with email address A and then with an Apple-ID that matches...