-
-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
single() returns Invalid media type: expected no more input. #921
Comments
I'm also having the same error. supabase: 1.11.11 |
Is that all stacktrace you get? Shouldn't there be some info about in which file and line it occurs? |
sorry, my bad, forgot to rethrow, here is the whole stack. [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Error on line 1, column 32: Invalid media type: expected no more input.
|
I think you have to use : |
It's possible temporary solution but with 30 .single() queries in prod, it was almost impossible to debug the first time where the issue happened at/neither to catch it |
@Mykyta-Chernenko @allipiopereira
Are you using the hosted version of Supabase? Does the same issue happen on a fresh Supabase instance? |
I get the error like this.
I use supabase hosted version. I tried to restart the db, the issue is still there I created a new db with the minimum migration, the issue is still there here is the migration I applied to the fresh db
I use Frankfurt region. Thanks for you help! |
I get the same error message, so I can confirm that. Also I get the same message if .single() is used and multiple results are returned. I tested supabase_flutter: ^2.3.4 and ^2.5.3. |
Having same issue |
Anyone facing this issue, would you be able to let me know what version of PostgREST you are running on the Supabase instance? |
Auth version |
Hmm, I aligned the PostgREST version, but am still unable to reproduce the issue. Is anyone willing to share their Supabase URL and Anon key so that I can make the query on my end to dig into this issue? Feel free to DM me on Twitter if you are not comfortable sharing them here. |
sent over twitter |
@Mykyta-Chernenko
final response = await supabase
.from('app_settings')
.select('review_version_ios, review_version_android')
.single(); I wonder what the difference between your environment and my environment could be. What platform have you tried? I have tried iOS and web, and didn't get the error that you are facing on either one of them. |
i have the same issue, here is my play around final response = await client.from('users').select().eq('id', userId);
if (response.isEmpty) return null;
return UserModel.fromJson(response.first); |
I upgraded the PostgREST version from 12.0.2 to 12.2.1 and Postgres version from 15.1.1.33 to 15.1.1.73. The weird error message is fixed now. |
I have same issue when I use rpc. final result = await supabase |
I had the same issue and upgrading to the latest version fixed the error 🚀 Auth version |
I would close this issue as it seems that upgrading the postgrest version seems to solve the issue. Anyone here still having the issue after upgrading? |
Describe the bug
When single() doesn't find anything, I get "Invalid media type: expected no more input."
full error
flutter: Event: MatchError, Properties: {error: Error on line 1, column 32: Invalid media type: expected no more input.
╷
1 │ application/json; charset=utf-8,application/vnd.pgrst.object+json; charset=utf-8
│ ^
╵}
flutter: Error fetching match: Error on line 1, column 32: Invalid media type: expected no more input.
╷
1 │ application/json; charset=utf-8,application/vnd.pgrst.object+json; charset=utf-8
│ ^
╵
To Reproduce
Steps to reproduce the behavior:
await supabase
.from('profile')
.select()
.eq('id', 'gibberish')
.single();
Expected behavior
Some ordinary exception as "not found"
Version (please complete the following information):
├── supabase_flutter 2.5.1
│ ├── supabase 2.1.1
│ │ ├── functions_client 2.0.0
│ │ ├── gotrue 2.6.0
│ │ ├── postgrest 2.1.1
│ │ ├── realtime_client 2.0.4
│ │ ├── storage_client 2.0.1
The text was updated successfully, but these errors were encountered: