The value is wrongly read as false when the current thread
doesn't have a TNSRuntime object associated with it. Instead of
calling [TNSRuntime current] use [TNSRuntime runtimeForVM:]
which will correctly find the object that matches the current
execution state.
[x] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
The value is wrongly read as
false
when the current thread doesn't have aTNSRuntime
object associated with it. Instead of calling[TNSRuntime current]
use[TNSRuntime runtimeForVM:]
which will correctly find the object that matches the current execution state.PR Checklist