You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The method sendResponse on class Communication with the argument closeAfterSending = true (code), should only close the connection after the deviceResponse message has been sent.
Actual Behavior
If the connection and or latency on the underlying mTransport is slow enough, the above described call will close the connection before the deviceResponse has actually been sent.
Steps to Reproduce the Problem
Open either the Purse or Wallet app on a real Phone (for my setup the emulator_speed/internet_speed ratio is too small to cause the race condition).
Go to a www-mdl-reader website and open a mdoc url.
Press the "Send data" button in the Purse or Wallet app.
The www-mdl-reader will receiver no data, since the app closed the connection before the data was sent.
Specifications
Platform: Android 14 Samsung Galaxy S21 5G
Fix
I'll open a PR with a fix in a minute
The text was updated successfully, but these errors were encountered:
nicklaswj
pushed a commit
to nicklaswj/identity-credential
that referenced
this issue
Jan 30, 2024
….transfer.Communication sendResponse
If `closeAfterSending` is true, only close the connection after we know the
`deviceResponse` payload have been sent.
….transfer.Communication sendResponse
If `closeAfterSending` is true, only close the connection after we know the
`deviceResponse` payload have been sent.
Signed-off-by: Nicklas Warming Jacobsen <[email protected]>
nicklaswj
pushed a commit
to nicklaswj/identity-credential
that referenced
this issue
Feb 1, 2024
….transfer.Communication sendResponse
If `closeAfterSending` is true, only close the connection after we know the
`deviceResponse` payload have been sent.
Signed-off-by: Nicklas Warming Jacobsen <[email protected]>
Expected Behavior
The method
sendResponse
on classCommunication
with the argumentcloseAfterSending = true
(code), should only close the connection after thedeviceResponse
message has been sent.Actual Behavior
If the connection and or latency on the underlying
mTransport
is slow enough, the above described call will close the connection before thedeviceResponse
has actually been sent.Steps to Reproduce the Problem
emulator_speed/internet_speed
ratio is too small to cause the race condition).Specifications
Fix
I'll open a PR with a fix in a minute
The text was updated successfully, but these errors were encountered: