fix: App cannot be started by user - WPB-24848#4777
Open
netbe wants to merge 3 commits into
Open
Conversation
Contributor
Test Results 17 files 1 193 suites 10m 49s ⏱️ For more details on these failures, see this check. Results for commit 8cf3756. ♻️ This comment has been updated with latest results. Summary: workflow run #26971611510 |
netbe
commented
Jun 1, 2026
Comment on lines
+111
to
+115
| let pathStream = AsyncStream<NWPath> { pathContinuation in | ||
| monitor.pathUpdateHandler = { pathContinuation.yield($0) } | ||
| pathContinuation.onTermination = { _ in monitor.cancel() } | ||
| monitor.start(queue: DispatchQueue(label: "CheckBlacklistWorker.NWPathMonitor")) | ||
| } |
Collaborator
Author
There was a problem hiding this comment.
this code is new, since the original code was not supporting iOS 16
|
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
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.



Issue
On C build, on special environment, the biometric prompt for EAR seemed not to happen especially on cold start. After more testing, it did happen but after 60 seconds after the blacklist check is done.
For some reason, the resolving of the url (which points to a 404, blacklist disabled on this environment) times out.
Solution:
Port fix of 4.18 to differ checking the blacklist from the userSession loading. See #4485
Testing
Run app on the special environment
Checklist
[WPB-XXX].UI accessibility checklist
If your PR includes UI changes, please utilize this checklist: