Can we access your project?
Current Behavior
All ListViews querying Supabase views crash with "Unexpected null value. The relevant error-causing widget was: Builder" originating from storage.dart. This happens specifically when a component receives Postgres time type columns (pickup_start_time, pickup_end_time) as parameters from a Supabase view.
Expected Behavior
Postgres time type columns from Supabase views should be handled correctly by FlutterFlow without crashing, the same way they worked before a schema refresh was performed.
Steps to Reproduce
- Create a Supabase view that includes columns of Postgres type time (e.g. pickup_start_time, pickup_end_time)
- Connect FlutterFlow to Supabase and import the schema
- Create a component with parameters that receive these time type columns
- Use this component inside a ListView querying the view
- Perform a schema refresh in FlutterFlow
- App crashes with "Unexpected null value"
Reproducible from Blank
Bug Report Code (Required)
IT4giMrl/YlPvt9c187pYe9V+GIROUA5U5c0sd4bGA0dCJzuPLMQdvXsYkxVXd/mYAk/JkSmmkwx+an5jvPXFfU5GAWbbJQ/1rlqcBWWeGG6QZOBCqisQEdtP8RnJ3aHy5+3vSR7LttoL3w96k+ABeqXHzDvHrrHIndISq/LZO4=
Visual documentation
Environment
- FlutterFlow version: 3.38.5
- Platform: Web
- Browser name and version: Google Chrome 148.0.7778.216
- Operating system and version affected: macOS Sequoia Version 15.7.4
Additional Information
This is blocking a pre-launch app. The issue started immediately after performing a schema refresh in FlutterFlow. The app worked correctly before the refresh with no code changes on our end. We have verified via Supabase REST API (Postman) that the view returns correct, complete data. Permission to access project: Yes — please use the PIKOP NO NOTIF or pikop test 1 project.
Can we access your project?
Current Behavior
All ListViews querying Supabase views crash with "Unexpected null value. The relevant error-causing widget was: Builder" originating from storage.dart. This happens specifically when a component receives Postgres time type columns (pickup_start_time, pickup_end_time) as parameters from a Supabase view.
Expected Behavior
Postgres time type columns from Supabase views should be handled correctly by FlutterFlow without crashing, the same way they worked before a schema refresh was performed.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4giMrl/YlPvt9c187pYe9V+GIROUA5U5c0sd4bGA0dCJzuPLMQdvXsYkxVXd/mYAk/JkSmmkwx+an5jvPXFfU5GAWbbJQ/1rlqcBWWeGG6QZOBCqisQEdtP8RnJ3aHy5+3vSR7LttoL3w96k+ABeqXHzDvHrrHIndISq/LZO4=
Visual documentation
Environment
Additional Information
This is blocking a pre-launch app. The issue started immediately after performing a schema refresh in FlutterFlow. The app worked correctly before the refresh with no code changes on our end. We have verified via Supabase REST API (Postman) that the view returns correct, complete data. Permission to access project: Yes — please use the PIKOP NO NOTIF or pikop test 1 project.