Ftrack: Manual sync breaks OP project if sync is done prior to prepare project

[BigRoy]

Running version

3.14.3

Describe the bug

Note: This happens with auto-sync disabled.

Whenever creating a new Ftrack project and having some assets/shots generated when clicking Actions > OpenPype Admin > OpenPype Admin - Sync to Avalon (Local) it syncs the project with fps, frame start, frame end, etc. values set to a None value.

I feel like this only really happens if we Create a new Ftrack project and Sync to Avalon before triggering the Actions > Prepare Project

Because on creating a new project - the project looks like this:

After Prepare project it looks like this:

Which is what I'd need.

To Reproduce
Steps to reproduce the behavior:

1. Create a new ftrack project
2. Do not trigger Actions > Prepare Project
3. Trigger Actions > OpenPype Admin > OpenPype Admin - Sync to Avalon (Local)

The project is now in a broken state in OpenPype since it has fps = None, frameStart = None, etc.

Expected behavior

I feel like we should DISALLOW the project to be synced without Prepare Project having triggered or when having these project values set to None. It should show a pop-up on what to do OR even better should automatically show the "Prepare Project" pop-up.

Screenshots

These are our ftrack defined custom attributes:

I feel like some of these aren't needed, are maybe old? and maybe the issue is that some don't have defaults to begin with?

Additional context

Came up on discord few times:

• here by Xavier Piveteau-Guyomarc'h — 12/06/2022 5:00 PM
• here by me — 09/06/2022 3:15 PM
• here by me - just now

Workaround

The active workaround to 'fix' it is to run Actions > Prepare Project and then Actions > OpenPype Admin > OpenPype Admin - Sync to Avalon (Local) again.

However I still feel the sync should still not work, or at least warn the user, if the attributes haven't been "prepared" correctly.

[cuID:OP-4870]

[BigRoy]

Irrelevant to AYON ftrack integration I believe.