Technically this is a workaround: Replacing the ProfileViewModel! with a real optional (or no optional at all) most probably requires a rewrite of the entire Profile-screen, including header etc. as the ProfileViewModel! is used basically everywhere.
So the workaround is to use the existing account (at least until it is updated and replaced) to not have the app crash when the user taps on their profile too quickly (without an account, which this PR fixes). For some reason, we persist the users very own profile, but never used it.
Technically this is a workaround: Replacing the
ProfileViewModel!with a real optional (or no optional at all) most probably requires a rewrite of the entire Profile-screen, including header etc. as theProfileViewModel!is used basically everywhere.So the workaround is to use the existing account (at least until it is updated and replaced) to not have the app crash when the user taps on their profile too quickly (without an account, which this PR fixes). For some reason, we persist the users very own profile, but never used it.