-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unity: Import Error Code:(4) #3376
Labels
App-type:Unity
Needs-Attention
Reporter has responded. Review comment.
O-Community
SDK-Use:Sync
T-Bug
Comments
This looks more like an issue with Unity itself. The Weaver doesn't modify itself, so there's no obvious reason why it would be responsible for changing the modify timestamp. |
nirinchev
added
the
Waiting-For-Reporter
Waiting for more information from the reporter before we can proceed
label
Jul 18, 2023
Yes, it appears to be related to something Unity changed in their version control and file-system monitoring when auto-refresh is off. Not your bug! Sorry :) |
github-actions
bot
added
Needs-Attention
Reporter has responded. Review comment.
and removed
Waiting-For-Reporter
Waiting for more information from the reporter before we can proceed
labels
Jul 19, 2023
No worries, happy to help! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
App-type:Unity
Needs-Attention
Reporter has responded. Review comment.
O-Community
SDK-Use:Sync
T-Bug
What happened?
While the project is recompiling, especially after updating the Realm package (which usually causes multiple of our assemblies to get recompiled on domain reload), sometimes the following error is given; logged as a warning.
Import Error Code:(4)
Message: Build asset version error: packages/io.realm.unity/editor/realm.unityweaver.dll in SourceAssetDB has modification time of '2023-07-08T01:31:54.27Z' while content on disk has modification time of '2023-07-10T09:30:49.8051328Z'
It may be that the Weaver is doing stuff at a time during the compilation/import/domain reload when it shouldn't.
Repro steps
Have multiple assemblies with RealmObjects and one depending on another; then update the realm SDK in the Unity Package manager.
Occasionally, the import error occurs, also on our automated build machines, which hold a cached version of the Library folder (including PackageCache). We suspect there are some issues with these failed, "non-error" condition Weaves that happen before the actual dll import is scheduled.
Version
11.2.0
What Atlas Services are you using?
Atlas Device Sync
What type of application is this?
Unity
Client OS and version
Windows 11 x64, Unity 2022.3.4f1 LTS
Code snippets
No response
Stacktrace of the exception/crash you're getting
Relevant log output
No response
The text was updated successfully, but these errors were encountered: