onScanResults never reached - BLE vs code

In blescan I just look for any scan result, but in things like the Nordic sample apps, they look for a specific UUID.  In blescan, do you see a UUID and does it match what you are looking for in your code?

If you are trying this in the sim, you you have the BLE hardware and has it been flashed with the proper hex file?

Right now I just set my state to scanning and im not searching for any device by uuid, just trying to see if

i can find the result by the device name. Should I have to register the profile just to scan?

i am doing this in the simulator and I have not flashed it with the proper hex file. How do I go about this? I'm pretty new to connect in and ble work. Thank you

See https://forums.garmin.com/developer/connect-iq/w/wiki/19/getting-started-with-connect-iq-ble-development

Last I checked, the dongle is about $10-$12US, but without that of the nRf52 DK, you can't use BLE in the sim.

I am having a similar issue in a custom app, with onScanResults() never being called after a start() call within the DeviceManager. 

The ble signal is being broadcasted by a custom device which is seen within the 'nRF Connect for Desktop Bluetooth Low Energy' app.  The nRF dev board has been programmed with the correct .hex file.

Currently running a 'Start Scan' within 'nRF Connect for Desktop Bluetooth Low Energy' and connecting the custom device to the dev board.  The app shows ble broadcast information.

Unsure where the issue is.  Is it correct to connect the ble device to the nRF dev board within the 'nRF Connect for Desktop Bluetooth Low Energy' app, or should the device remain disconnected in the desktop app when scanning from within the CIQ app (simulator)?

Any direction on this would be appreciated.  Unsure if this is an issue within monkey c app or the way we have things configured within the nRF Connect environment.

Ok, so if I understand correctly you have one Nordic board and it's flashed for the nRfConnrct Desktop, and not for the sim.  The sim can't use it then, so it doesn't see any BLE.  Maybe flash it for the sim and then use nRFConnect on a phone?

You can also install BleScan on your Garmin.  It will show you all devices that CIQ Ble can see,

https://apps.garmin.com/apps/9bcc8b66-8385-4afb-b93e-f69e01422284

One thing, i you will probably see devices in nRFConnect you don't see on the Garmin, and no name where you expect one or no UUID where you expect one.

Not much you can do about that unless you have the code for the sensor.

The dev board has been flashed with the connectivity_2.0.1_115k2_with_s132_5.0.hex found here:

https://forums.garmin.com/developer/connect-iq/w/wiki/19/getting-started-with-connect-iq-ble-development

After which the device is selected in the nRF Connect desktop app through the 'select device' (within the desktop app) shown here:

Then the custom app is ran in vscode in attempt to work BLE within the simulator, where the onScanResult() isn't called (as described above).

What I am hearing jim_m_58 is that after flashing the dev kit with the .hex file, is to stay out of the nRF Desktop app with that dev kit and just run the CIQ custom app to perform the scan?  Would that be accurate?

Yes.  Once the board is flashed with the proper file, close nRFConnect, maybe turn off the board and back on, and look for it's com port and set that in the sim

In the link you posted, see

Finding The COM Port

COM port was previously verified as connected.

Will follow your suggestions and see if this can get working.

This approach fixed the issue.  onScanResults() is now being called as expected.