Ben Wunderlich

We have the same problem and moving to `careflow/netlify-actions/cli@master` does not change it. Has someone a solution for the problem? In case it helps here is the full output of...

Sorry, ignore me. The replacement works like a charm, I just didn't notice that there was a second use with `netlify/actions/cli@master`. Thanks 👍

Hi, I see similar behaviour on the example app. `registerOneOffTask` is doing nothing, but when I trigger "Simulate background fetch" the app crashes with these logs: ```sh 2022-08-23 09:58:10.185987+0100 Runner[2719:70633]...

Thanks for the quick response @Vinzent03. That is a very good point the current production version is still on `gotrue 1.4.2`: ```txt ├── supabase_flutter 1.4.0 │ ├── supabase 1.5.1 │...

Thank you very much Vinzent03. We actually have a new release going out to the first users today, which uses 1.5.6. I will keep you posted if the new version...

Sorry I meant we are on 1.5.7 😅

@Vinzent03 we rolled out our new app version to some test device. So far everything looks good. But we got this error yesterday and it seems to be stuck in...

Hi @Vinzent03, we had yesterday again a user that didn't get log out even though the request returned 401 codes. Is there anything that we could miss when we listen...

Thanks for the quick response @Vinzent03. If it helps, this is full response: ``` Response Headers: access-control-allow-origin: "*" content-type: "application/json; charset=utf-8" x-kong-upstream-latency: "0" alt-svc: "h3=":443"; ma=86400, h3-29=":443"; ma=86400" via: "kong/2.8.1"...

I can see the 100 failed requests and they all tried to fetch the same resource: ```json { "status": 401, "response_time": 198.431, "method": "GET", "response_headers": { "access-control-allow-origin": "*", "content-type": "application/json;...