Currently, the device status check job is not being cancelled when the 'Cancel' button is clicked before the QuickConnect status check succeeds. This was a miss when porting from 2.x. While this is a not usual case, it is still possible to Cancel the flow when waiting.
As a solution invoke QuickConnectManager.cancel() when Cancel is clicked.
Related Issue
Motivation and Context
Currently, the device status check job is not being cancelled when the 'Cancel' button is clicked before the QuickConnect status check succeeds. This was a miss when porting from 2.x. While this is a not a usual case, it is still possible to Cancel the flow when waiting.
As a solution invoke QuickConnectManager.cancel() when Cancel is clicked.
How Has This Been Tested?
Unit tests
Manual tests using assurance test app.
Screenshots (if appropriate):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
Currently, the device status check job is not being cancelled when the 'Cancel' button is clicked before the QuickConnect status check succeeds. This was a miss when porting from 2.x. While this is a not usual case, it is still possible to Cancel the flow when waiting.
As a solution invoke QuickConnectManager.cancel() when Cancel is clicked.
Related Issue
Motivation and Context
Currently, the device status check job is not being cancelled when the 'Cancel' button is clicked before the QuickConnect status check succeeds. This was a miss when porting from 2.x. While this is a not a usual case, it is still possible to Cancel the flow when waiting. As a solution invoke QuickConnectManager.cancel() when Cancel is clicked.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: