You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case the app was launched and while put into background the toAttributedString() was called which caused the exception. When debugging the method was called on the main thread, however enforcing the method to be called on the main thread wrapping it in DispatchQueue.main.async {} seems to fix the issue.
The question is if something similar could be done in the library code itself, only thing is that it will require some callbacks instead of return types as it is now.
The text was updated successfully, but these errors were encountered:
iwasrobbed
changed the title
Crash when using toAttributedString while app is in background
[Down] Crash when using toAttributedString while app is in background
Nov 13, 2018
iwasrobbed
changed the title
[Down] Crash when using toAttributedString while app is in background
[Down] Can't render toAttributedString while app is in background
Dec 20, 2018
Report
What did you do?
Used the toAttributedString() method.
What did you expect to happen?
No crash.
What happened instead?
Got the following issue report from Crashlytics:
In my case the app was launched and while put into background the toAttributedString() was called which caused the exception. When debugging the method was called on the main thread, however enforcing the method to be called on the main thread wrapping it in
DispatchQueue.main.async {}
seems to fix the issue.The question is if something similar could be done in the library code itself, only thing is that it will require some callbacks instead of return types as it is now.
This one might help solving the issue: #100
The text was updated successfully, but these errors were encountered: