Handshake error for some users #143
Replies: 5 comments 23 replies
-
|
Based on: at Supabase.Functions.Client.HandleRequest (System.String url, System.String token, Supabase.Functions.Client+InvokeFunctionOptions options) [0x001e3] in <3e0c6dc7a762481390541dccc1ca3c02>:0
at Supabase.Functions.Client.Invoke (System.String functionName, System.String token, Supabase.Functions.Client+InvokeFunctionOptions options) [0x00093] in <3e0c6dc7a762481390541dccc1ca3c02>:0 It looks like it could be an issue with a supabase function that's being called... |
Beta Was this translation helpful? Give feedback.
-
|
WRT to testing the access, I would add the hello or timestamp pingback request before you call your auth method. Try adding some debug tracing before and after the steamResponse fetch and parsedData lines. If you have the specific ID info for the failing clients I would see if you can capture the complete req you have coming in to Deno.serve as well. Add logging or debug to the Deno.serve top level as well to see what you can get out. The lines that are jumping out at me just looking at it are the Authorization coming from the request and then passing directly in to the steamResponse fetch. That fetch is happening in the Deno.serve, so if something goes wrong it's going to pop it up to the top level. In this scenario I think what would happen is the steamResponse fails with an auth rejection, then it passes it to the Deno.serve which in turn passes that up to your client. FWIW I don't think this has much to do with supabase-csharp but now it's a mystery... :) |
Beta Was this translation helpful? Give feedback.
-
|
I was able to push a dev build and have found that the "SignInWithSteam" portion in that error log is on the line where I do the following: The supabase object is an instance of a Supabase.Client. It appears it blows up on the Invoke. However, the supabase logs actually show the successful authentication with valid data (from the auth.txt I posted before...the actual file is called steam-verify) ...which is very confusing. |
Beta Was this translation helpful? Give feedback.
-
|
I don't understand why the Invoke would work to the point that supabase gets the logs from the steam-verify edge function like it completes successfully but this error occurs anyways...I would expect a different error if it is during the deserialize call. |
Beta Was this translation helpful? Give feedback.
-
|
I confirmed that I get this error if I move the Invoke outside of the deserialize code...so the issue doesn't involve the deserialize. |
Beta Was this translation helpful? Give feedback.
-
|
@wiverson or @acupofjose Do you have any ideas on this with the new info? |
Beta Was this translation helpful? Give feedback.
-
|
My two cents - either there is something weirdly wrong with the Unity TLS (eg the stuff in an earlier post) or there is something weird about the incoming data interacting with the function. At this point I think you're looking at having to figure out either how to recreate using deeper and deeper logging to get every scrap of input and output and/or attaching a debugger to a test server. I'm leaning toward it not being the Unity TLS stuff as it would presumably affect other things, but if it's only this one function that points to something about the function and the data. |
Beta Was this translation helpful? Give feedback.
-
|
Unity is out of my wheelhouse personally, but I agree with @wiverson that it'd be odd for it to blow up in this case and only this case. Since your supabase logs show a successful authentication with steam and it blows up afterwards I'm also inclined to say it's a issue with the data being returned. But I don't understand why Unity would say it's a TLS error if that's the case.... Nor do I understand why Unity would throw the TLS error and the request be sent to the supabase servers too. All I have is a 🤷 as an answer unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
RE Unity and the TLS, well... umm... Unity can be (cough) a bit quirky. Especially when they decided for some reason to write their own special version of a standard library like JSON processing or networking. So the notion that, say, there's an exception where a https fault gets wrapped by the wrong exception doesn't surprise me at all thb. |
Beta Was this translation helpful? Give feedback.
-
|
So the people that are having an issue are accessing the edge function from a different region than what the database is on. So supabase's suggestion is to set the region for it in the headers during the invoke call. https://github.com/orgs/supabase/discussions/12613 |
Beta Was this translation helpful? Give feedback.
-
|
Do you have any insight into that? I know the supabase c# logic is split into multiple repos and I wasn't really seeing what I needed to change to expose it right away. |
Beta Was this translation helpful? Give feedback.
-
|
Sure! I'd add the timeout as an option to Mondays are my busy day, I can do an Issue and PR tomorrow for it if you like! |
Beta Was this translation helpful? Give feedback.
-
|
That would be great! Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Should be good to go in the latest release |
Beta Was this translation helpful? Give feedback.
-
|
Awesome thanks! Also, fun unrelated note, calling the GetPublicUrl() on a bucket is giving me back a url with the bucket name in it twice which breaks the url. |
Beta Was this translation helpful? Give feedback.
-
|
Oof, turns out it is a bug in Unity TLS. Someone forgot to put @UnityAlex I assume you work for Unity, so you might want to fix this in their repo. |
Beta Was this translation helpful? Give feedback.
-
|
Oh no! Yes I do work for Unity. If someone could submit a bug to us I would be happy to investigate and fix. |
Beta Was this translation helpful? Give feedback.
-
|
@UnityAlex Has this been handled? If not I can submit the issue wherever you'd like. |
Beta Was this translation helpful? Give feedback.
-
My team has found an issue where authorization with supabase gets a handshake error but we are having a hard time reproducing. The two people that have had the issue are both on Mountain time...which leads me to think it may be a time zone issue. I have tried using a VPN to reproduce the issue but with no luck. The users with the issue are able to get around it if they use a VPN. Here is the error we get:
Beta Was this translation helpful? Give feedback.
All reactions