Currently PIN based connection error codes and quick connect error codes exist separately. This distinction is not need and can be unified similar to Assurance iOS.
Unify AssuranceSocketError and AssuranceQuickConnectError to AssuranceConnectionError.
Add AssuranceConnectionError as a parameter to session status notifications to provide details of termination if any. This is useful for presentations like QuickConnect for managing their lifecycle by registerting as session status listeners as it is a native activity where dependency injection is not possible and reference to the activity/presentation for notifying chanages is not available.
Related Issue
Motivation and Context
Currently PIN based connection error codes and quick connect error codes exist separately. This distinction is not need and can be unified similar to Assurance iOS.
How Has This Been Tested?
Unit tests.
Smoke tests with test app.
Screenshots (if appropriate):
Types of changes
[ ] 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 PIN based connection error codes and quick connect error codes exist separately. This distinction is not need and can be unified similar to Assurance iOS.
AssuranceSocketErrorandAssuranceQuickConnectErrortoAssuranceConnectionError.Related Issue
Motivation and Context
Currently PIN based connection error codes and quick connect error codes exist separately. This distinction is not need and can be unified similar to Assurance iOS.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: