Copied layer paths absolute even when set to relative, remain linked to original datasource

[MatparMcWolfie]

When exporting a project using the plugin, layers set to "copy" in cable export settings get an absolute path instead of a relative one. The geopackage are created in the target folder but the layers remain linked the original datasource.

This bug mainly happens when I export to a folder on the same drive as the main project, although I'm not exactly sure it's systematic.

You can find a copy of the main project with datasources as well as an example of an export for offline use here: https://drive.google.com/drive/folders/1byZuBSrtt-rSFKXHBJn0bk-Bhk7Nl9-y?usp=drive_link

QGIS 3.38.3
QFieldsync 4.10.1
Windos 11

[Skipper-is]

Same issue here - Windows 10,
QField v4.12.0
QGIS 3.34.11
Have to go in manually and edit the file paths after export to get it to work

[FelixHinckel]

I have the same problem for months, and I just figured out something :
When I want to make a package from a project that I have just created, it works fine.
When I want to make a package from a project that is already a QFieldSync package, the paths stick to the old package data.
I have the same issue for cloud uploading.

Seems like the act of packaging via QFieldSync switch all paths to absolute, even if QGIS displays them as relative (at least when trying to package again).

Is it something that is volontary? Is there a way to switch back to relative path, maybe through the console?

Windows 11
QGIS 3.34.6-Prizren
QFieldSync 4.12.1