as dm3d mentioned, we have tried to reproduce by sharing a Vuforia project between PC and Mac, but were unable to reproduce it.
Also, You mention:
Simply exchange a project between a mac and a pc.
Have you tried to do the same using a basic Vuforia project with an ARCamera and one Image Target for example ? As, this would help, i.e. it but would be good to be have a clearly reproducible case that you can share, if possible.
Also, I assume you are aware of the following Unity guidelines (which do not apply specifically to Vuforia, but are generally applicable to any Unity project):
- There are two ways to share projects between multiple machines (be from Win to Mac or between two of the same kind):
- Packaging the project as a unitypackage and importing it at the other machine
- Sharing the Assets and ProjectSetting folders of a project between the computers (e.g. via a repository or by just copying them). In particular, the Library folder must not be shared.
Note that the second approach is basically equivalent to the first (i.e. using unitypackages), as the only difference is basically in that the unitypackages adds a packaging (zipping) step on top.
We know that certain issues may occur (mostly editor crashes or infinite import loops) if the Library folder is shared (and so it should not be shared, as stated above).
This can even happen sometime just when switching between two repository branches (in a version control system) of a project without deleting the local Library folder. This is however a Unity-specific issue, not specifically related to Vuforia. Unity explicitly instructs developers to exclude the Library folder from versioning.
So, since, as you say in your last message, using the unitypacke export + import technique solves the issue for you too, you can try to see if perhaps the error message you used to get when using the original approach was due to the sharing of the Library folder.