Wrong expression used for photos

[signedav]

The customer configures the expressions in QFieldSync, but they are not considered.

When having a look at the QGS file it seems, that there is a backwards compatibility issue.

<customproperties>
  <Option type="Map">
          <Option name="QFieldSync/attachment_naming" type="QString" value="{&quot;Foto1&quot;: &quot;'SAGU' || '/' || format_date(now(),'yyyyMMddhhmmsszzz') || '.{extension}'&quot;, &quot;Foto3&quot;: &quot;'Foto3' ||  '/'  || 'test_'|| format_date(now(),'yyyyMMddhhmmsszzz') || '.jpg'&quot;}"/>
          <Option name="QFieldSync/photo_naming" type="QString" value="{&quot;Foto1&quot;: &quot;'DCIM/pn-protokoll-gruppe_' || format_date(now(),'yyyyMMddhhmmsszzz') || '.jpg'&quot;, &quot;Foto3&quot;: &quot;'DCIM/pn-gruppe_' || format_date(now(),'yyyyMMddhhmmsszzz') || '.jpg'&quot;}"/>
          [...]
  </Option>
</customproperties>

In QFieldSync he configures what is stored as attachment_naming but what QField uses is what is stored in photo_naming.

QField: 2.6.3
QFieldSync: 4.3.1
QGIS: 3.22.5

[signedav]

The issue in the end is that QField 2.6.3 reads photo_naming while QFieldSync 4.3.1 writes attachment_naming.
QField Master apparently reads attachment_naming. @nirvn I'm pretty sure what it is about. Apparently QField is a step behind QFieldSync. Shouldn't there be a backwards compatibility fallback in QField or QFieldSync?