During our usage of this library, there are a lot of crashes revolving around DispatchQueuePool. Therefore we replaced it with the built-in ThreadPoolExecutor, which ideally provides the same functionality. We didn't see any visual impact and can safely assume that this change works well.
During our usage of this library, there are a lot of crashes revolving around
DispatchQueuePool
. Therefore we replaced it with the built-inThreadPoolExecutor
, which ideally provides the same functionality. We didn't see any visual impact and can safely assume that this change works well.