Description
we currently have a couple of Modules in the app that track certain values (eg, language, time zone, measurement system, etc) and write the values into the account details.
problem: as it turns out, if this happens too quickly after the app is launched, it can (somehow?) interfere with the regular initial account details loading, and ends up putting the app into a state where the only details present are those that were written by the app on launch, and all other details somehow end up not being added to the local AccountDetails.
Reproduction
easiest to see: delete the app while being logged in, then reinstall while forcing a firebase env being loaded on launch. for the entire onboarding, all account-details-persisted fields will be empty (can be seen by logging the .detailsChanged event, or by looking at the demographics section and seeing that it is all empty)
Expected behavior
good question. clearly the code we have in MHC should just work as-is, but it's not obvious where the fix should be.
we can fix it directly in MHC, but the underlying issue is (seems to be?) SpeziFirebase not handling its initial details load correctly
Additional context
it seems like this issue only occurs in some cases.
Code of Conduct
Description
we currently have a couple of Modules in the app that track certain values (eg, language, time zone, measurement system, etc) and write the values into the account details.
problem: as it turns out, if this happens too quickly after the app is launched, it can (somehow?) interfere with the regular initial account details loading, and ends up putting the app into a state where the only details present are those that were written by the app on launch, and all other details somehow end up not being added to the local AccountDetails.
Reproduction
easiest to see: delete the app while being logged in, then reinstall while forcing a firebase env being loaded on launch. for the entire onboarding, all account-details-persisted fields will be empty (can be seen by logging the .detailsChanged event, or by looking at the demographics section and seeing that it is all empty)
Expected behavior
good question. clearly the code we have in MHC should just work as-is, but it's not obvious where the fix should be.
we can fix it directly in MHC, but the underlying issue is (seems to be?) SpeziFirebase not handling its initial details load correctly
Additional context
it seems like this issue only occurs in some cases.
Code of Conduct