I don’t see a direct solution for this. The best solution is to move both to the same domain, safari is very strict with 3rd party cookies and will block them by default. Also other browsers will do this in the future when they are not already doing so.
Both Safari & Chromium browsers are causing this issue.
There are numerous posts pointing to secure & sameSite cookie settings, which allows 3rd party cookies.
How can I check if Wappler is doing that? I don’t see any option other than in the config.js file. I am not using security provider.
The application is supposed to work like a widget on a third-party-domain, so same domain is not an option at all.
There are other providers for whon the setup works fine - like Twilio, BotsCrew etc - which are chat applications that inject their iframe on the page and have cookies as well.
So I’m sure Wappler is missing some setting here.
I don’t think they use cookies in the widgets, there is not a workaround for the cookie blocking. What you can do is using a different way to keep the state, like on the client you could use the localStorage or an old way is by passing the state (sessionid) in the querystring.
We changed the logic to use a local variable. We did not need the information to be stored on browser, so did not use localStorage. Instead just passing the value from a variable in each request.