giorgio
07/01/2022, 12:22 PMMatB57
07/01/2022, 12:52 PMYeehawlerz101
07/01/2022, 2:20 PMYour email address [My Email] does not match the email address this invitation was sent to.
Murkrage
07/01/2022, 2:25 PMKennyMurders
07/01/2022, 2:53 PMNicoNico
07/01/2022, 3:05 PMccc159
07/01/2022, 6:52 PMapp.supabase.com
? By default the OAuth takes me directly to https://gitab.com
user
07/01/2022, 10:54 PMMike_
07/01/2022, 11:49 PMjs
const { data, error } = await supabase
.storage
.from('public-assets')
.list('accounts/c36a689f-484b-46fb-aac2-9ad397603009', {
limit: 16,
offset: 0,
sortBy: { column: 'created_at', order: 'desc' },
})
// Data returned is []
I've attached a screenshot of the bucket within the UI (It's set to public and has 4 assets in it)
Any ideas on why this may be happening? It appears I'm making the same API call on my app's network tab as the supabase UI's network tab when listing these assets, but the response is different. Is it a permissions/RLS thing?gerry
07/02/2022, 2:11 AMawait supabase.auth.user(jwt)
and supabase.auth.api.getUser(session.access_token)
both return null and return a "Could not read User ID claim" error.
I am using a third party auth provider and manually generating the JWT using the JWT secret. does this mean I'm not actually signing in the users? i followed the instructions from this tutorial https://medium.com/@gracew/using-supabase-rls-with-a-custom-auth-provider-b31564172d5djar
07/02/2022, 2:38 AM_res := jsonb_set(_res, '{myval}', to_jsonb(7.8::float));
like why cant i just do
_res->'myval' := 7.8::float;
or somethingLEGEND
07/02/2022, 12:11 PMNeedle
07/02/2022, 12:37 PMJoão Vitor
07/02/2022, 2:54 PMKayden
07/02/2022, 3:45 PMsamjmck
07/02/2022, 4:27 PMTeiem
07/02/2022, 5:18 PMsupabase db remote commit
errors with Error: unexpected end of JSON input
Needle
07/02/2022, 8:08 PMMike_
07/02/2022, 8:17 PMsamjmck
07/02/2022, 10:05 PMSalvage_Dev
07/02/2022, 10:44 PMaulia
07/02/2022, 10:50 PMAlanK
07/03/2022, 1:48 AM..,/endpont.js
export const post = async ({ locals, request }) =>
withApiAuth(
{
user: locals.user
},
async () => {
const body = await request.formData();
const bodyObject = setMissing(getFormBody(body));
const { data: surveyAnswers, error } = await supabaseServerClient(request)
.from('profile')
.update({
first_name: bodyObject.first_name,
family_name: bodyObject.family_name
if (error) {
console.log('update error profileCommunity:', error);
return {
status: 400,
body: { error }
};
}
console.log('Data: ', surveyAnswers);
return {
status: 200,
body: { surveyAnswers }
};
}
);
VuNguyen
07/03/2022, 7:35 AMcassideous
07/03/2022, 9:39 AMSalvage_Dev
07/03/2022, 10:40 AMglomyst
07/03/2022, 10:53 AMez-klik
07/03/2022, 2:41 PMMurkrage
07/03/2022, 2:59 PMauth.verifyOTP()
in NextJS and subsequently redirecting to the page that you should now have access to, it unfortunately redirects the user straight back to login. Here's the code that I'm using:
ts
const verifyOTP = async () => {
const { user, error } = await supabaseClient.auth.verifyOTP({
email: getValues('email'),
token: getValues('otp'),
type: 'magiclink',
});
if (error) {
console.log('Error while verifying OTP', error);
return;
}
if (user) {
console.log('Logged in');
setTimeout(() => {
console.log('redirecting to recipes');
router.push('/recipes');
}, 1500);
}
};