We've having this log spammed, and there doesn't seem to be way to silence it
-[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
-[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
-[mot_LEConnectivityMgr startDiscovery] Discovery is not started due to incorrect central manager state
It also appears that there are two empty space print outs after every `-[mot_LEConnectivityMgr...` log. Screenshot from VSCode attached - the ( 2 ) in the screenshot is indicating that line was printed twice, the line being an empty line (or maybe just two spaces or a tab or something)
I've found two other forum posts that say it should have been resolved in version 1.4.30, but I'm on 1.4.39 and it doesn't seem to be fixed. Was there a logging option added that I'm just not seeing?
This is making it extremely hard to debug our app.
5 Replies
Hi, any update on this? Thanks
Hi, any update on this? These logs make it very difficult to debug our app, and we're considering ditching Zebra for another bluetooth device.
Hi, people asked this for years. There is no good answer yet unfortunately.
Hi, people asked this for years. There is no good answer yet unfortunately.
Hello, the ZD421 is connected via USB. We are using Browser Print v1.3.2.489, and the most recent JavaScript library is installed. The Browser Print client program has been completely removed and reinstalled this year.
When I attempted to print the test on the demo site, I continued to receive the following problem messages even though I had added https://techdocs.zebra.com/emdk-for-xamarin/8-0/guide/maui/ geometry dash as an allowed site.