chore: do not check blacklist when loading user session - WPB-24175#4485
Conversation
…er-session-WPB-24162
Test Results 6 files 621 suites 5m 20s ⏱️ For more details on these failures, see this check. Results for commit f51ac26. ♻️ This comment has been updated with latest results. Summary: workflow run #23546619988 |
Test Results – WireFoundationAll53 tests 53 ✅ 9s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
Test Results – WireSyncEngine1 095 tests 1 095 ✅ 1m 33s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
Test Results – Wire-iOS1 881 tests 1 854 ✅ 2m 8s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
Test Results – WireShareEngine15 tests 15 ✅ 0s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
Test Results – WireDomain 1 files 137 suites 16s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
Test Results – WireUIAll160 tests 159 ✅ 1m 5s ⏱️ Results for commit e753cbd. ♻️ This comment has been updated with latest results. |
…-session-WPB-24175 # Conflicts: # wire-ios/Wire-iOS/Sources/AppStateCalculator.swift
|



Issue
When loading a user session we currently check the blacklist. Under poor networking conditions this can lead to poor UX - a user might have to wait 60 seconds on the loading screen before a time out occurs and they are navigated to the conversation screen.
This PR:
CheckBlacklistWorkerwhich intermittently checks the blacklist and cause the block view to be shown if the build is blacklisted for a particular logged in server. The app does a check just after loading the users session then again every 6 hours. It also does re-checks if those have failed (based on network condition changes and every 30 min).checkBuildBlacklistActionrecurring action as this is handled by the above workerTesting
0via Developer menu -> Overrides & quit the app.Checklist
[WPB-XXX].