Hi, I am struggling with multiple logs that are printed in console from your iOS SDK every half of a second!!! I think that - (SBT_RESULT) sbtEnableAvailableScannersDetection:(BOOL)enable;
method produces those. These are very annoying and makes hard to find really important information in Xcode console.
I saw you already had similar thread.. but it was closed with no resolution, at least I did not find any there.
Please suggest any way how to turn those logs off.
Thank you!
021-04-29 10:59:15.483225+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:15.984171+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:16.485667+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:16.987090+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:17.487801+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:17.989156+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:18.490549+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:18.991990+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:19.493443+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:19.994359+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2021-04-29 10:59:20.495350+0300 -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
Is there a way to remove annoying console logs -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect// Expert user has replied. |
3 Replies
Older SDK versions prior to 1.4.30 will have this situation.
Zebra Engineering updated this on the latest versions. found here:
https://www.zebra.com/us/en/support-downloads/software/developer-tools/…
Could you please say how this can be disabled? We are using the latest SDK and still get this:
2022-01-05 13:55:43.963872+0100 ***[7889:3317934] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataTimestamp value 663080143.961705
2022-01-05 13:55:43.964380+0100 ***[7889:3317934] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxPrimaryPHY value 0
2022-01-05 13:55:43.964751+0100 ***[7889:3317934] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxSecondaryPHY value 0
2022-01-05 13:55:43.965296+0100 ***[7889:3317934] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataTxPowerLevel value 8
2022-01-05 13:55:43.965860+0100 ***[7889:3317934] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataIsConnectable value 1
2022-01-05 13:55:44.726650+0100 ***[7889:3318017] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] Discovered (null)
...
2022-01-05 13:55:45.642931+0100 ***[7889:3317710] -[mot_LEConnectivityMgr processDetectionResults] Peripheral is NOT detected by current discovery procedure but IS still connected - do NOT process disappearance
Hi, any update to this? We just updated to iOS SDK 1.4.39 and we're still getting these logs spammed