Filter out logging for [mot_LEConnectivityMgr] (iOS)

// Expert user has replied.
M Michael Wells 3 years 6 months ago
124 6 0

I'm using the symbolbt-sdk (Zebra Scanner) iOS SDK. It works well, but when debugging in Xcode the debug console is flooded with messages from [mot_LEConnectivityMgr ...] which makes debugging difficult. Since there is so much output from that API, my app logging is hidden a bit.

Is there some way to turn this logging off? I'm assuming it's using NSLog, but since I don't have the source code I can't remove this logging myself. It would be ideal if there was a way on calling SbtSdkFactory.createSbtSdkApiInstance() that you could pass in an optional logging field? Or if there is better way?

If I'm missing something obvious, any help is much appreciated.

Thanks!
Please Register or Login to post a reply

6 Replies

F Felipe Gomez 5 years 2 months ago

Need solution to this very annoying issue... you are constantly dumping logging to the console and make it very hard to debug other problems... Please Help!
2019-08-27 09:00:56.407520-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:56.909501-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:57.411408-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:57.913330-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:58.415611-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:58.917554-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:59.419373-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:00:59.921384-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2019-08-27 09:01:00.423387-0400 alliance-pos-ios-dev[4289:1470417] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state

C Caleb Jones 5 years 6 months ago

Yes, please, this is extremely annoying.

L Luke Carpenter 3 years 2 months ago

Please can we get a setting to configure this? The logging is super excessive.

S Sean Kennedy 2 years 11 months ago

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/…

S Sean Kennedy 2 years 11 months ago

Another issue you may encounter even with the newer SDK is if you have "OPMODE_ALL" configured, when "OPMODE_MFI" is used the Verbosity will be reduced. (iOS solutions use MFi {Made for Iphone bluetooth} for iOS <-> RFD8500)

F FirstName LastName 2 years 6 months ago

The newest version 1.4.32 outputs different log messages, but the original problem is not really solved.
Would it be possible to include a switch where developers can turn off logging?
Or is this just debugging logs left in place in a production build?
<code>
2022-04-22 08:21:43.701945+0200 PISA[42566:1680720] -[mot_SDKHandler sbtSetOperationalMode:] Remove incompatible devices for new op mode
2022-04-22 08:21:43.702061+0200 PISA[42566:1680720] -[mot_SDKHandler sbtEnableAvailableScannersDetection:] Perform discovering once option becomes enabled
2022-04-22 08:21:43.702284+0200 PISA[42566:1680904] -[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
2022-04-22 08:21:44.231347+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] Discovered CS6080 20304520100385
2022-04-22 08:21:44.231562+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataManufacturerData value {length = 8, bytes = 0xf101435336303830}
2022-04-22 08:21:44.231704+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataTimestamp value 672301304.229672
2022-04-22 08:21:44.231822+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataIsConnectable value 1
2022-04-22 08:21:44.231904+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxPrimaryPHY value 0
2022-04-22 08:21:44.231985+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxSecondaryPHY value 0
2022-04-22 08:21:44.232110+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataLocalName value CS6080 20304520100385
2022-04-22 08:21:44.232794+0200 PISA[42566:1680906] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataServiceUUIDs
2022-04-22 08:21:44.248991+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] Discovered (null)
2022-04-22 08:21:44.249153+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataTimestamp value 672301304.2464809
2022-04-22 08:21:44.249274+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxPrimaryPHY value 0
2022-04-22 08:21:44.249354+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataRxSecondaryPHY value 0
2022-04-22 08:21:44.249436+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataTxPowerLevel value 7
2022-04-22 08:21:44.249507+0200 PISA[42566:1680911] -[mot_LEConnectivityMgr centralManager:didDiscoverPeripheral:advertisementData:RSSI:] key kCBAdvDataIsConnectable value 1
</code>

The last lines repeat every 20 seconds for every bluetooth device in the environment.

CONTACT
Can’t find what you’re looking for?
Get in touch