Wappler Version : 3.7.6
Operating System : Windows10
Server Model: Node API & EXPRESS App
Expected behavior
Data should be refreshed with sockets.
Actual behavior
No data is rendered at all inside the repeat, when applying the sockets
How to reproduce
So I have created a Node api, which works perfectly and returns data.
I have built my first hello world electron app which shows said data inside a repeat. The problem arises when I enable sockets. Nothing is rendered.
I did try that suggestion, as you can see from the screenshot of the code, but alas to no avail.
I have recreated this bug inside a standard NODEJS server model website project, rather than an App project…….I think the problem is with the absolute url path…(which you must have in an app).
One server connect works, and the other does not…….
I’m not sure how to go about that on the link you sent…
I have the cors option set within Wappler
…and yes, I was able to recreate the issue within the same server/project…… please see screenshot of the code above… it happens when you enter the absolute url in the path for server connect
It appears that this url which I had to enter manually seems to be the issue when running the app…………Wappler generates wrong code that points to a local url. …src=“socket.io/socket.io.js”