fix(app-management): surface app list failures instead of caching an empty list - #489
Merged
Merged
Conversation
KazuCocoa
approved these changes
Aug 16, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 16, 2026
## [1.92.4](v1.92.3...v1.92.4) (2026-08-16) ### Bug Fixes * **app-management:** surface app list failures instead of caching an empty list ([#489](#489)) ([f2d38a4](f2d38a4))
|
🎉 This PR is included in version 1.92.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On a real iOS device
getInstalledAppsfetches the User and System app lists throughPromise.allSettledso that a failure on one type does not discard the other. When both lookups fail, the loop still produces an empty array and that empty list is cached for the full 60s TTL.Two things go wrong from there:
No installed app matched the name <name>instead of the actual device error, which points at the wrong problemname-based lookup keeps failing the same way for a minute, even after the device recovers, because the empty list is served from the cacheRethrow the first rejection when every lookup failed, so the driver error reaches the caller and nothing is cached. Partial failures keep the existing behaviour. This also matches the Android/simulator branch, which already lets the failure propagate.