Closed zmoshansky closed 2 years ago
After clearing app storage, everything works properly on Android... However, this is obviously not a workable solution for a production app.
Hi @zmoshansky 👋 Thanks for opening an issue!
Are you able to provide a link to a minimal reproduction sample? Thanks!
I'm going to close this as I strongly suspect this underlying issue is the root cause of the issue (Many reported bugs around corruption).
Description I've added a new
hydratedCubit
to an app (Android), that has already persisted data, and upon callingHydratedStorage.build
it errors. The cubit I added has a single required fieldString id
, and is built with freezed (AFAICT, shouldn't matter). When running the app inside a fresh web-browser profile (storage is clear) everything works fine.I'm unsure if this is a Hive issue, or an issue with HydratedBloc's use of Hive.
Steps To Reproduce 1.) Create an App with a hydratedCubit 2.) Launch app and have cubit save state 3.) Add a new
hydratedCubit
to the app 4.) CallingHydratedStorage.build
it errors from Hive.Expected Behavior This should just work, or cause some error in my deserialization code.
Additional Context When running the app inside a fresh web-browser profile (storage is clear) everything works fine. This also relates to https://github.com/felangel/bloc/issues/2613 w