Popout window is not responding to heartbeats

[shipswake]

I have implemented heartbeats and when an app is opened in an iframe the heartbeats work as expected.

I am able to open a new window as a popout and connect to the FDC3 DA. The FDC3 channels are connected, and messaging works as expected.

When opened as a popout window, I notice that the DA sends the heartbeat, but a response is never received.

Mosaic Server Context Post: {type: 'heartbeatEvent', meta: {…}, payload: {…}} 80956bd0-c481-437e-aba8-448749d31b6a

Do you know what might be missing for the app opened in a new window to respond to the heartbeat?

[robmoffat]

Are you implementing a desktop agent?

[kriswest]

Are you using the reference DA implementation in /toolbox/fdc3-for-web/demo or implementing your own? I think @robmoffat and I were both unclear on whether its a custom implementation or you are reporting an issue with the reference implementation (which should have test covering this...)

[kriswest]

Note an app doesn't have to do anything about heartbeats - they should happen entirely between the proxy code getAgent uses and the DA implementation, hence, if it works with the reference implementation then its likely the DA implementation we need to be thinking about to help you.

[shipswake]

we are using
import { getAgent } from '@finos/fdc3';

[kriswest]

That's the 'client-side', i.e. the app. What about the desktop agent side?

[shipswake]

We have our own Desktop Agent implementation. I'll compare it to the /toolbox/fdc3-for-web/demo

[kriswest]

If you can see the message being sent, then you could check in the application whether its being received (at all vs. not handled properly vs. received and responded to but mishandled at the DA end) by setting the logLevel argument:

await getAgent({logLevels: {connection: LogLevel.DEBUG, proxy: LogLevel.DEBUG}})

LogLevel.DEBUG == 4 I think.

You must have messaging working to use other features, the question is: whats up with the heartbeat messages?
I would compare behaviour (if you are implementing a Desktop Agent) to the reference implementation in /toolbox/fdc3-for-web/demo using the same log settings and see what differences you see. If you can tell us about that we may be able to help further.

[shipswake]

I updated the log levels.
In the main browser window 2 heartbeat requests sent.
In the log for the main browser window, I see the heartbeat response.

In the second browser window I see the other heartbeat response.

Seems this is working as expected.