Invalid argument null with type Null

[bsutton]

When I start my system sqflite is reporting:

Invalid argument null with type Null.
Only num, String and Uint8List are supported. See https://github.com/tekartik/sqflite/blob/master/sqflite/doc/supported_types.md for details

This will throw an exception in the future. For now it is displayed once per type.

I would love to fix this but no contextual information is provided that might help me to track down what entity is causing the problem.

The system needs to include the entire map that is being process or at least the entity name so that you can find the source of the issue. A stack trace would also be useful.

[alextekartik]

I have added the print of the stack trace in sqflite_common: 2.5.4+2 just published

[bsutton]

thanks!

…

On Sat, Aug 17, 2024 at 9:06 PM Alexandre Roux ***@***.***> wrote: I have added the print of the stack trace in sqflite_common: 2.5.4+2 just published — Reply to this email directly, view it on GitHub <#1125 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG32OBOYKPXL36BWAXWIADZR4VDZAVCNFSM6AAAAABMVEAF52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHAZDOOJWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bsutton]

Only issue is that the error has gone away and I don't believe I've made any changes to the start up code that was generating the error.

…

On Sat, 17 Aug 2024, 11:13 pm Brett Sutton, ***@***.***> wrote: thanks! On Sat, Aug 17, 2024 at 9:06 PM Alexandre Roux ***@***.***> wrote: > I have added the print of the stack trace in sqflite_common: 2.5.4+2 > just published > > — > Reply to this email directly, view it on GitHub > <#1125 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAG32OBOYKPXL36BWAXWIADZR4VDZAVCNFSM6AAAAABMVEAF52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHAZDOOJWGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[alextekartik]

Weird has the change is minimal: 7867d39
Since it happens when an argument is null (so requires to check anywhere that could happen which can be painful) maybe the context has changed...
Good luck in reproducing!