Getting errors related to logging

[morpho]

The application seems to stop at an instance where I invoke a Send call to send data over to a ble central, and the callstack looks as follows. Any way to narrow down the cause?

I tried the program later and I got the following stack. Thing is: nothing useful gets printed in the debug console

[morpho]

the advertising data is only useful when the peripheral is connected to the central though no? is sending data when the peripheral isn't even connected any good? but just advertising a base UUID has nothing to do with connection; from what I understand, it just allows the central to see the advertised peripheral in the scan list.

and you only see the attribute table after the connection is established, and i'm indeed using my custom service characteristics  which are passed to sd_ble_gatts_characteristic_add as well as sd_ble_gatts_service_add for adding a custom service.

Are you fully certain it has nothing to do with the nRF Connect app which has previously been found to be buggy?

[morpho]

It indeed was the issue with the nRF Connect app as I had imagined. There was no my custom service wouldn't initialize and rather something that I wasn't initializing (NUS) would get picked up...for some reason.

why is the length supposed to 2 here though when looking for CCCD handle?

if ( (p_evt_write->handle == pCust->rxCustomValueHandle.cccd_handle) && (p_evt_write->len == 2))

[Hung Bui]

There is a chance that the phone cached the ATT table (so that it doesn't need to do service discovery every time you connect to it) and it explain why you see the older version of the Att table. 

The way to avoid that is to have SERVICE_CHANGED characteristic in the Att table. It's to tell the phone not to cache the att table. You can do that by enabling NRF_SDH_BLE_SERVICE_CHANGED in sdk_config.h 

[morpho]

thanks. I'll try.

Can you also please answer my latest question?

[Hung Bui]

Sorry I forgot to answer the 2nd question. By spec the CCCD characteristic is 2 bytes, even though only the last byte is used so usually to enable notification you need to write 0x0001 and to enable indication you do 0x0002.