Rather explicitly call authenticationManager.initialize()

Author: adborbas

WooCommerce/Classes/AppDelegate.swift

@@ -57,6 +57,8 @@ class AppDelegate: UIResponder, UIApplicationDelegate {
         let analytics = ServiceLocator.analytics
         let pushNotesManager = ServiceLocator.pushNotesManager
         setupAnalytics(analytics)
+        ServiceLocator.authenticationManager.initialize()
+        ServiceLocator.stores.initializeAfterDependenciesAreInitialized()
 
         setupCocoaLumberjack()
         setupLibraryLogger()

WooCommerce/Classes/SceneDelegate.swift

@@ -21,12 +21,6 @@ final class SceneDelegate: UIResponder, UIWindowSceneDelegate {
         self.appCoordinator = coordinator
         coordinator.start()
 
-        /// IMPORTANT:
-        /// `AppCoordinator.start()` must be called before this, so that
-        /// AuthenticationManager.initialize() has already initialized WordPressAuthenticator.
-        /// See AuthenticationManager.hasInitializedAuthenticator and restoreWordPressSite().
-        ServiceLocator.stores.initializeAfterDependenciesAreInitialized()
-
         // Scene-scoped initializations that need UI
         setupNoticePresenter()
         setupUniversalLinkRouter()

WooCommerce/Classes/ViewRelated/AppCoordinator.swift

@@ -238,7 +238,6 @@ private extension AppCoordinator {
 
     /// Configures the WPAuthenticator for usage in both logged-in and logged-out states.
     func configureAuthenticator() {
-        authenticationManager.initialize()
         authenticationManager.setLoggedOutAppSettings(loggedOutAppSettings)
         authenticationManager.displayAuthenticatorIfLoggedOut = { [weak self] in
             guard let self, self.isLoggedIn == false else { return nil }