stream returns invalid response about supabase-dart

[JasonChiu-dev]

Hi @phamhieu It works correctly now. Thank you so much for your inform and help.

[phamhieu]

Hi @JasonChiu-dev supabase-dart: ^0.2.13 is deployed. Let me know if it works for you.

[Vinzent03]

I don't think my changes in #82 are the reason, because I didn't change anything on insert. I guess the bug is in 0.2.11.

[JasonChiu-dev]

1. The stream bug happened since yesterday. And my supabase package's setup on pubspec.yaml file was: supabase: ^0.2.10 at the beginning.

2. On Thu, 13 Jan at 2:06 PM, I reported an error to Supabase tech team:
   Hi, It worked ok about one hour ago, but I can not log into Supabase now and shows error message: "LateInitializationError: Field 'changedAccessToken' has not been initialized.". How can I solve this problem?? Need help. Jason Chiu

3. On Thu, 13 Jan at 3:53 PM, the Supabase tech team reply:
   The error has been resolved by this PR #84.. Can you checkout the latest supabase-dart.
   ​Please let us know if the problem persists. Thank you.
   Best,
   Hieu

4. Then I upgrade the setup of pubspec.yaml to: supabase: ^0.2.12

5. I can login Supabase correctly, but the stream bug(the stream replace my correct row with wrong row which change my original data to "null".) show up. That means the correct row data really insert into the database table successfully, but the stream fetch the data and change many columns' data with null.

6. All the story happened in these two days.

For your information.

[JasonChiu-dev]

5. That means the correct row data really insert into the database table successfully, but the stream fetch the data and change many columns' data with null.

The insert action is correct. It means the correct row data really insert into the database table successfully, but the stream fetch the data and change many columns' data with null. This is the real problem.