Since the new iOS18 Update on iPhone we get the following Warning when using push():
WARN com.vaadin.flow.server.communication.ServerRpcHandler -- Resynchronizing UI by client's request. A network message was lost before reaching the client and the client is reloading the full UI state. This typically happens because of a bad network connection with packet loss or because of some part of the network infrastructure (load balancer, proxy) terminating a push (websocket or long-polling) connection. If you are using push with a proxy, make sure the push timeout is set to be smaller than the proxy connection timeout
wich leads into a white screen. The App needs to be refreshed after that.
In my dev machine I only use tomcat 10, no vpn, no loadbalancer or similar. The Connection is stable as well.
The problem only occures if i use the ssl connector of the tomcat. With HTTP their is no problem, but this is not the solution.
Expected behavior
No Warning
Minimal reproducible example
We use the @Push annotation at our main route. The problem occures if we want to update the UI from an backround task with
UI.getCurrent().access(() -> { UI.getCurrent().push() });
Description of the bug
Since the new iOS18 Update on iPhone we get the following Warning when using push():
WARN com.vaadin.flow.server.communication.ServerRpcHandler -- Resynchronizing UI by client's request. A network message was lost before reaching the client and the client is reloading the full UI state. This typically happens because of a bad network connection with packet loss or because of some part of the network infrastructure (load balancer, proxy) terminating a push (websocket or long-polling) connection. If you are using push with a proxy, make sure the push timeout is set to be smaller than the proxy connection timeoutwich leads into a white screen. The App needs to be refreshed after that.In my dev machine I only use tomcat 10, no vpn, no loadbalancer or similar. The Connection is stable as well. The problem only occures if i use the ssl connector of the tomcat. With HTTP their is no problem, but this is not the solution.
Expected behavior
No Warning
Minimal reproducible example
We use the @Push annotation at our main route. The problem occures if we want to update the UI from an backround task with
UI.getCurrent().access(() -> { UI.getCurrent().push() });Versions