-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In iOS 13, using Apple .systemFont will use the incorrect font if a paragraph style is set. #1701
Comments
You can use ASTextNode2 instead of ASTextNode. |
Is this #1579 ? |
@atkalikov I would be willing to try this, but I literally have hundreds of cases I am working with here. Is there any documentation on the differences between |
Also, I don't know if this is any help, but |
@dirtmelon Would you be able to create a PR that has a test for this? It would be terrific to back fill these tests. Thanks. @Sethmr Please try with master. |
@bolsinga I will attempt tomorrow. |
Ran into this myself yesterday. Couldn't get it working with latest from master either. Font displayed fine without paragraph style. Wonder if you found the same @Sethmr? |
Sorry, I meant in your attempt today. Will have to dig into why it wasn't working for me with master. |
I am facing the same issue. When will you guys release the new version with the fix of this issue? |
Hello. Today is December 4th. Can you release at least a little hotfix for this problem? |
Would love a fix. |
After using the XCode 11 compiler, the
.systemFont
started having incorrect cases of font app wide for us. After looking deeper into the problem, I found that every time you use the.paragraphStyle
in any way shape or form (even with an empty initializer) on yourNSAttributedString
it will cause Times New Roman to be displayed instead of SF Fonts.My team uses this extensively in our app and would highly appreciate a fix. I will attempt to find a work around in the mean time that is acceptable. Thanks for a great framework to build upon :).
Example below:
The text was updated successfully, but these errors were encountered: