Priority: P2: Important
Affects Version/s: 5.15.5
Fix Version/s: None
Component/s: Remote Objects
With a .rep file like this:
If on the client side (replica), we connect the signal to the slot
The waitForFinished always end in timeout.
If we go with a QRemoteObjectPendingCallWatcher to do that asynchronously, it works as expected.
I guess it's related to the signal "connection" still open while we do the second call or something related to the eventLoop but was not expecting this behavior.
I attached a small project that show the bug. launch it without argument for the server, with -c for the client (triggering timeouts) and with -c -a for the asynch client (working)
Is there something that I'm doing wrong or is it a proper bug?