Bug report: HealthKit Sample Upload Before Firebase Login about spezitemplateapplication HOT 4 OPEN

I'm not sure where the original rationale came from to refresh the token upon app start. I think it might make sense to keep that to e.g. have a smooth experience when there are external changes to your account.

But I agree, we should aim for getting the Account details ready faster (at least partially, e.g., it might take a while to load the user details from an external storage provider. Otherwise, we could choose to cache that on disk as well.)

from spezitemplateapplication.

@Supereg We have resolved this in the TBI app by adding the Firebase configuration module as a dependency of the Standard and manually using the Firebase functions to obtain a cached user.

It would be good to explore how we might automate that setup that Spezi Firebase Auth code and Account injection somehow is guaranteed to run before a HealthKit data type could arrive?

from spezitemplateapplication.

So what you are doing in TBI is directly accessing Auth.auth().currentUser which is present from the start?

What we currently do in SpeziFirebase is to force refresh the auth token upon app startup. This code was kept from the original version of SpeziAccount/SpeziFirebase. We could choose to remove that altogether, which should improve configuration time of the SpeziFirebase module. I assume, Firebase would automatically refresh the token before you do the next request.

from spezitemplateapplication.

Yes, that is the current approach we follow in TBI.

I think it is good to inject the account as early as possible. We can still do the token refresh once we already set the user as signed in and provided all the information right on the startup?

from spezitemplateapplication.