Need to handle subsequent video start service ACKs not setting the video resolution height and width

[NicoleYarroch]

Bug Report

The first video start service ACK received from Core always has the video resolution in the payload. However subsequent video start service ACKs during the same session sometimes set the video resolution to {0, 0}. This is an issue with the streaming video using TCP socket as a secondary transport as the video session must be destroyed when the app on the device is backgrounded and resumed when the app on the device is foregrounded. Currently the library assumes that the video start service ACK always returns the resolution in the payload so if {0, 0} is returned video can not stream due to the video encoder rejecting 0 as a dimension.

Reproduction Steps

1. Connect a video streaming app with secondary transports enabled to a head unit that supports secondary transports for video streaming. Launch the SDL app if necessary and wait for video to start streaming.
2. Put the app in the background.
3. Bring the app to the foreground.

Expected Behavior

Video resumes.

Observed Behavior

Video does not resume due to the video start service ACK returning a resolution of {0, 0} in the payload.

OS & Version Information

• iOS Version: 13
• SDL iOS Version: 6.5
• Testing Against: SYNC 4

[NicoleYarroch]

Fixed in PR #1566