MissingFrag bit set after succesful FUOTA

[brushlow-TELLUS]

Hi there,

I'm running FUOTA with fragmentation package v1, LNS is AWS, LBM is release branch v4.8.0. Everything runs successfully with no missed packets, but the fragmentation session status answer sets the third byte to 1, indicating that there is one missing fragment. I confirmed this by adding frag_decode_status.MissingFrag to a print in fragmentation_package_parser(); the MissingFrag looks to countdown to 0 as expected, but remains at 1 upon receipt of the final fragment:

Current fragment index = 1,
Current fragment counter = 40,
Number of missed packets = 0,
Missing frag = 2,
--> RP_STATUS_RX_PACKET
lr1mac_class_c_mac_rp_callback
lorawan_fragmentation_package_service_downlink_handler receive data on port 201
Fuota fragmentation_package_rx_window 4
I (861612) smtc_hal: FUOTA size: 9020

Fuota session info : 
Current fragment index = 1,
Current fragment counter = 41,
Number of missed packets = 0,
Missing frag = 1,
--> RP_STATUS_RX_PACKET
lr1mac_class_c_mac_rp_callback
lorawan_fragmentation_package_service_downlink_handler receive data on port 201
Fuota fragmentation_package_rx_window 4
I (864682) smtc_hal: FUOTA size: 9240

Fuota session info : 
Current fragment index = 1,
Current fragment counter = 42,
Number of missed packets = 0,
Missing frag = 1,
 FILE RECONSTRUCTS SUCCESSFULLY !

...

lorawan_fragmentation_package_service_downlink_handler receive data on port 201
Sending fport: 201, data: 01 2a 40 01 00 

I then see the MissingFrag error indicated in AWS.