-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
feat: uninstall the test app once and install that again when MismatchedApplicationIdentifierEntitlement installation error occurs #2050
Conversation
Updated some changes, especially offload application case, that requires explicit I'll update further later. |
On my local testing, I observed that when app installation failed, such a case also the "offload" state happened. So, the most easiest way to reproduce this is:
So, actually this case requires app deletion explicitly to avoid before the app installation. I'll update this branch further |
Updated |
@@ -0,0 +1,122 @@ | |||
import chai from 'chai'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
## [5.5.0](v5.4.1...v5.5.0) (2023-10-02) ### Features * uninstall the test app once and install that again when MismatchedApplicationIdentifierEntitlement installation error occurs ([#2050](#2050)) ([0c561f5](0c561f5))
🎉 This PR is included in version 5.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I saw an app installation got failed as mismatch provisioning profile identifier error even the OS did not have the given bundle id on the device via
isAppInstalled
check.So, according to
isAppInstalled
, the app should not be on the device but an installation error occurred since the app was installed with another provisioning profile.Not clear the reason, but based on the device log, potentially the OS internally cached some information. Some installation steps worked, but haven't been completed. The uninstall (device.remove) could help to clear such cache.
Another note in my investigation related to this, if the app under test remained in the device as an offload app (maybe not "cache"), the app is not "present" on the device (
isAppInstalled
is false, expected based on the available information) but the OS keeps the data.driver.remove
uninstalls all of them for sure.Thus, current fullReset/enforceAppInstall capabilities won't clear the local data if the application remains as offline application. Users must call
mobile: removeApp
explicitly to call the remove method for sure,