Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync env-aware-quick-connect with main #146

Merged
merged 7 commits into from
Nov 6, 2024
Merged

Conversation

prudrabhat
Copy link
Contributor

Sync env-aware-quick-connect with main

prudrabhat and others added 7 commits August 29, 2024 14:52
We are seeing occasional  instances where the app AndroidManifest content
being sent by the Assurance SDK as part of client event is not the actual
manifest of the app- and it is for the WebView library.

Currently this is being seen in automation tests and we have not be able to
root cause this issue but it seems to be some case of bad android manifest
read from the system itself.

Given that the package name can be programmatically retrieved (as opposed to
the current way of reading the entire manifest), this change  adds a
device side detection of this wrong package name scenario and then force correct
it on device before sending the client event as a best effort these cases.
[MOB-21662] Validate and fallback to known manifest (3.x)
Merge `dev-v3.x` into `staging` for Assurance 3.0.4
Merge `staging` into `main` for Assurance 3.0.4
@prudrabhat prudrabhat merged commit 95590af into env-aware-quick-connect Nov 6, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant