Processing of individual vehicle data result codes in SubscribeVehicleData/UnsunscribeVehicleData responses from HMI
Bug Report
Processing of individual vehicle data result codes in SubscribeVehicleData/UnsunscribeVehicleData responses from HMI
Reproduction Steps
- SDL and HMI are started
-
SubscribeVehicleData,UnsunscribeVehicleDataare allowed by policies - App is subscribed to e.g speed data
- App requests
SubscribeVehicleData(gps) - HMI responds with
SubscribeVehicleData(resultCode:SUCCESS, gps = { resultCode = <not success code from VehicleDataResultCode structure> }) - App requests
UnsubscribeVehicleData(speed) - HMI responds with
UnsubscribeVehicleData(resultCode:SUCCESS, gps = { resultCode = <not success code from VehicleDataResultCode structure> })
Expected Behavior
TBA
Observed Behavior
- SDL sends
SubscribeVehicleData(resultCode:SUCCESS, gps = { resultCode = <not success code from VehicleDataResultCode structure> })response to mobile app and subscription is not created internally - SDL sends
UnsubscribeVehicleData(resultCode:GENERIC_ERROR, gps = { resultCode = <not success code from VehicleDataResultCode structure> }, info = "Unsubscription failed for some Vehicle data")response to mobile app and unsubscription is failed internally
OS & Version Information
- OS/Version: Ubuntu 18.04
- SDL Core Version: https://github.com/smartdevicelink/sdl_core/commit/bb4a6fb4d44bf86bd66d4827718d393244b8078e
Test Case, Sample Code, and / or Example App
SubscribeVehicleData_SmartDeviceLinkCore.zip UnsubscribeVehicleData_SmartDeviceLinkCore.zip
@GetmanetsIrina Is this issue still reproducible on the latest develop commit
@ShobhitAd, yes, the issue is still reproducible on the latest develop commit (2f002290411cae9a414c4dfccc93bb777a9482d0)
@GetmanetsIrina I see, thanks for verifying.
I'm currently not able to reproduce the issue on my end. Could you kindly send me your logs of the test with the latest develop commit? Just so I have a better idea as to what steps I'm missing