As per the above image - when we use .start() function on page tracking from the iOS sdk - we see this purple warning in Xcode - is there a way to resolve this?
Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions
Hi Gareth Lloyd -what version of the iOS SDK are you on?
With the release of SDK version 1.45 (our release notes), these warnings should have been significantly reduced.
To give you some background - The issue is occurring because FullStory is divided into two main components: the platform specific data gathering component and the cross platform data management component. The data management component requires initialization, but it typically runs on background threads so that it does not impact app performance. Also for performance reasons, FullStory waits to initialize the data management component until it is needed, but if a foreground thread triggers initialization, that thread will momentarily wait on the data management background thread.
The good news is that as far as we can see, this issue has very low user impact and v1.45 of our SDK significantly reduces the occurrences of this.
Our team has a long term goal of improving the data management architecture. We would appreciate any feedback from customers such as yourself that informs us of how this issue impacts your end users. Based on this feedback, we may be able to make a short term improvement to address any such scenarios.
Comments
3 comments
Hi Gareth Lloyd -what version of the iOS SDK are you on?
With the release of SDK version 1.45 (our release notes), these warnings should have been significantly reduced.
To give you some background - The issue is occurring because FullStory is divided into two main components: the platform specific data gathering component and the cross platform data management component. The data management component requires initialization, but it typically runs on background threads so that it does not impact app performance. Also for performance reasons, FullStory waits to initialize the data management component until it is needed, but if a foreground thread triggers initialization, that thread will momentarily wait on the data management background thread.
The good news is that as far as we can see, this issue has very low user impact and v1.45 of our SDK significantly reduces the occurrences of this.
Our team has a long term goal of improving the data management architecture. We would appreciate any feedback from customers such as yourself that informs us of how this issue impacts your end users. Based on this feedback, we may be able to make a short term improvement to address any such scenarios.
Please let us know of any questions!
Hi Uday - thanks for your quick response - i am currently using the most up to date SDK version - 1.47.0.
I haven't noticed any user impacts in relation to this, but with any of these warnings in Xcode it is highlighting that there is an issue.
Thanks for the explanation - appreciate the complexity around this one and looking forward to a solution in the future.
I still see this warning on Full Story version 1.50.0 but it's intermittent
Please sign in to leave a comment.