Support Forum

Ask a Question
Back to all

High Hang Rate Reported in TaboolaSDK v4.0.10 – Request for Fix Confirmation

Hi Taboola Support Team,

Apple has flagged that within the TaboolaSDK (version 4.0.10), we are experiencing a 87%, 90% hang rate, which appears to be linked to the code blocks shown below (as per Apple's diagnostics).

1-

TaboolaDK: +[TBLLocationService is
LocationServicesAvailable] + 216
87% of hang time

v start dyld
main The Weather Channel v static App.main() SwiftUl v ScriptMessageHandlerDelegate::didPostMessage(WebKit::WebPageProxy&, WebKit::FramelnfoData&&, API:
v -[TBLWebViewManager userContentController:didReceiveScriptMessage:] TaboolaSDK
v -[TBLUtils performFromClass:strSelector:parameters:] TaboolaSDK
v -[NSInvocation invokel CoreFoundation
<invoking-
CoreFoundation
v -[TBLWebViewManager getDeviceData] TaboolaSDK
v -[TBLDataManager getDeviceDataWithUnitDeviceData:] TaboolaSDK
v -ITBLUnitDeviceData getDeviceData] TaboolaSDK
v -[TBLUnitDeviceData getAdditionalData] TaboolaSDK
v -[TBLUnitDeviceData location] TaboolaSDK
v +[TBLLocationService isLocationServicesAvailablel TaboolaSDK
_dispatch_semaphore_wait_slow

2-

TaboolaSDK: -[TBLDeviceData
language] + 384
90% of hang time

v start dyld
v main The Weather Channel v static App.main () SwiftUl
v ScriptMessageHandlerDelegate::didPostMessage(WebKit::WebPageProxy&, WebKit::FramelnfoData&&, API
v -[TBLWebViewManager userContentController:didReceiveScriptMessage:] TaboolaSDK
v -[TBLUtils performFromClass:strSelector:parameters:] TaboolaSDK
v -[NSInvocation invoke] CoreFoundation v invoking CoreFoundation
v -[TBLWebViewManager getDeviceData] TaboolaSDK
v -[TBLDataManager getDeviceDataWithUnitDeviceData:] TaboolaSDK
v -[TBLUnitDeviceData getDeviceData] TaboolaSDK
v -[TBLUnitDeviceData getAdditionalData] TaboolaSDK
v -[TBLDeviceData getGlobalAdditionalDataDictionary] TaboolaSDK
v -[TBLDeviceData language] TaboolaSDK
+[UlTextInputMode

We would like to confirm whether these specific issues has been addressed in a more recent version of the SDK. If so, could you please provide:

The version where the fix was implemented

Any relevant release notes or migration considerations

We are evaluating whether an upgrade is needed on our end and would appreciate your guidance.

Thank you,