NukeStudio getting registered twice

[tokejepsen]

Hey,

I'm getting the NukeStudio application registered twice on a machine.

With the old API we had to do a check; https://bitbucket.org/ftrack/ftrack-connect-rv/commits/6af970df438f, but how do you do that in the new api?

[Lucas Correia]

Hi Toke,

The hook for the Nuke Studio action includes a check to verify that it is only registered for the new API (see source here).

Have you set any of the following environment variables on the machine when launching connect?

• FTRACK_EVENT_PLUGIN_PATH
• FTRACK_CONNECT_PLUGIN_PATH

 

Regards,
Lucas

[tokejepsen]

Hey Lucas,

 

Yes, both FTRACK_EVENT_PLUGIN_PATH and FTRACK_CONNECT_PLUGIN_PATH are set. I'm running from source.

10 minutes ago, Lucas Correia said:

The hook for the Nuke Studio action includes a check to verify that it is only registered for the new API (see source here).

I thought this was only to check whether its registered for the new api rather than the old, and not whether the action itself has already been registered.
I have only noticed it on one machine though.

[Lucas Correia]

Yes, you are correct in that that is the reason. Since we discover plugins for both the new and the old API in connect that check is necessary.

Looking at the code it looks like the plugin might be registered twice if the FTRACK_EVENT_PLUGIN_PATH is pointing to a path that is already included in either FTRACK_CONNECT_PLUGIN_PATH  or the default ftrack-connect-plugins directory. Is this the case for you?

[tokejepsen]

Turns out the machine had multiple versions of ftrack-connect installed along with running the ftrack-connect from source.

Uninstalling all the ftrack-connect versions solved the problem.

Thanks for Lucas for the guidance

[Lucas Correia]

Aha, that would also cause this issue. 

No problem, and thanks for following up.