BLE_GAP_EVT_ADV_REPORT missing complete local name?

Question

Hello - 
 
 This is a strange problem and I'm guessing I am missing something obvious. I am using the sd_ble_gap_scan_start() API to perform active scanning as follows: 
 
 ble_gap_scan_params_t scan_params;

	gBLE->adv_report_buffer.len = sizeof(gBLE->adv_data);
	gBLE->adv_report_buffer.p_data = &gBLE->adv_data[0];
	
	c_memset(&scan_params, 0, sizeof(scan_params));
	scan_params.active = 1;
	scan_params.filter_policy = BLE_GAP_SCAN_FP_ACCEPT_ALL;
	scan_params.interval = interval;
	scan_params.window = window;

	err_code = sd_ble_gap_scan_start(&scan_params, &gBLE->adv_report_buffer);
 
 The length of the advertising report data buffer is set to BLE_GAP_SCAN_BUFFER_MAX. In my GAP event handler, I receive the BLE_GAP_EVT_ADV_REPORT events and the associated report data record: 
 switch (p_ble_evt->header.evt_id)
{
case BLE_GAP_EVT_ADV_REPORT: {
ble_gap_evt_adv_report_t const * p_evt_adv_report = &p_ble_evt->evt.gap_evt.params.adv_report; 
 When I examine the bytes in p_evt_adv_report->data.p_data, there are no device name fields in the advertisement/scan response data. The p_evt_adv_report->data.len field value seems viable. I know I have multiple peripheral devices advertising their complete local names. I can see them in LightBlue and various other mobile BLE scanning apps. In my code I do follow-up and restart scanning after each BLE_GAP_EVT_ADV_REPORT event: 
 sd_ble_gap_scan_start(NULL, &gBLE->adv_report_buffer);
 
 Is there a configuration/initialization option I am missing that would lead to this behavior? 
 
 I am running this code on the nRF52840 DK under FreeRTOS. 
 
 Regards, 
 Brian