Device engagement bytes are double encoded when performing reverse engagement(Over the Internet)

[vaimut]

Expected Behavior

deviceEngagementBytes should come as #6.24(bstr .cbor DeviceEngagement) but it is encoded again during device retrieval process

Actual Behavior

double encoded deviceEngagementBytes

Steps to Reproduce the Problem

Try over the internet(18013-7) verification with the below reader https://www-s.nist.gov/mdl/ and check the flow with the app holder and as per document as well it should come as a tagged 24 byte string but in DeviceRetrievalHelper it's been encoded again to cbor

It should come as
{"deviceEngagementBytes": 24(h'A30063312E31018201D818584BA401022001215820CC8C76E13101C50A9FF0849CE77135B824C88AD703293F969F0BD4549AE00EF2225820888EB057805D35BD08500533792B09D32800707BD029B130D77D148A3EE1A5DB0581A363636174016474797065016764657461696C73A166646F6D61696E60')'}

but it work's as
{"deviceEngagementBytes": h'D8185877A30063312E31018201D818584BA401022001215820CC8C76E13101C50A9FF0849CE77135B824C88AD703293F969F0BD4549AE00EF2225820888EB057805D35BD08500533792B09D32800707BD029B130D77D148A3EE1A5DB0581A363636174016474797065016764657461696C73A166646F6D61696E60}

Specifications

• Version:
• Platform: