The Main thread would run a performAndWait invocation against a background Core Data MOC
A sequence of events would result in a Tracks Event being fired
And Tracks locking everything up, because the main thread is busy
In this PR we're caching, at launch, the TracksDeviceProperties.
I do realize this approach ain't perfect: Orientation is bond to change, and preferred content size could be altered as well. This changeset is a compromise solution.
Details:
We've observed a deadlock affecting DayOne where:
performAndWaitinvocation against a background Core Data MOCIn this PR we're caching, at launch, the
TracksDeviceProperties.I do realize this approach ain't perfect: Orientation is bond to change, and
preferred content sizecould be altered as well. This changeset is a compromise solution.Feedback welcomed, thanks in advance!!