Factory Reset

[mikeymike9000]

I was struggling to 'update' a Factory singleton, in this case a Firestore instance . I think I figured it out but was hoping for confirmation.. e.g. I don't think there's a need to re-register in Step 3b?

extension Container { public var firestore: Factory { self { Firestore.firestore() }.singleton }

1. Container.shared.myDataRepo.resolve().removeAllFirestoreListeners()

2a) Auth.auth().signOut()
2b) Firestore.firestore().terminate()
2c) Firestore.firestore().clearPersistence
2d) FirebaseApp.app()?.delete

3a) Container.shared.firestore.reset()
3b) NOT NEEDED? —> Container.shared.firestore.register { Firestore.firestore() }

4a) FirebaseApp.configure()
4b) Auth.auth().addStateDidChangeListener
4c) Auth.auth().addIDTokenDidChangeListener

5. Container.shared.myDataRepo.resolve().firestore = Container.shared.firestore()

6. sign back in to Firebase and prosper..

Does all this look ok?

[hmlongco]

What may or may not be an issue is that resetting the cache only ensures that the next injected value that's asked for gets a new value. Any previously injected or resolved values will still exist, and will not be replaced.

Instead of attempting to reset singleton caches, it's usually better to create a manager that tracks the current instance. One that can be cleared as needed.

class FirestoreManager {

    private(set) var current: Firestore?

    func logout() throws {
        // do whatever
        current = nil
    }
    
}

This way anyone who's asked for a FIrestoreManager still has one, and as long as they always go through current you can be sure they're talking to the right one.

Even better, if possible, would be to hide current and funnel all access through the manager's functions.

[mikeymike9000]

thanks for the rapid response! in Step 5 above I manually update the previously injected value (after removing existing firestore listeners so there are no dangling resolved values): Container.shared.myDataRepo.resolve().firestore = Container.shared.firestore()

but yes I see this is non-reactive yuckiness

so for your suggestion, do you mean:

extension Container { public var firestoreManager: Factory< FirestoreManager> { self { FirestoreManager() }.singleton }}

public class AccRepo: ObservableObject {
  @Injected(\. firestoreManager) private var firestoreManager: FirestoreManager
  someFunc() {
    firestoreManager.current.someFireFunc()
  }
}

[hmlongco]

Can do that. Just need to make sure no one tries to grab and persist their own copy of current.

[mikeymike9000]

awesome thanks Michael, so much better. when i find the time i'm still def going to try out Navigator

[mikeymike9000]

ok tested it and works like a charm.. here are the order of operations i'm using for firebase signout, clearPersistence, reinstantiate:

1a) remove all firestore listeners
1b) Auth.auth().signOut()
1c) firestoreManager.currentFirestore.terminate()
1d) firestoreManager.currentFirestore.clearPersistence
1e) FirebaseApp.app()?.delete

2a) FirebaseApp.configure()
2b) Auth.auth().addStateDidChangeListener
2c) Auth.auth().addIDTokenDidChangeListener

3. firestoreManager.currentFirestore = Firestore.firestore()

4. user signs back in and prospers..