-
Notifications
You must be signed in to change notification settings - Fork 165
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
No properties in xxxRealmObject #3631
Comments
➤ PM Bot commented: Jira ticket: RNET-1160 |
How does |
I'm not sure what the status of the DLL file is during the build process because we first compile it using HybridCLR before proceeding with the build process. I noticed in the packaging log that weaving was automatically executed during the execution of the BuildPlayerScripts script, and theoretically it should be correct by the time WriteFileList is executed. However, my current guess is that maybe the DLL loaded into memory is still from before weaving, which causes an error. |
|
@nirinchev
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
What happened?
I get the exception while my project building in the batch mode.
The WriteFileList is a build task in my SBP like this:
And the GetFileListFormFilePath in AssetManager.cs is:
This exception only occurs in the batch mode!
I firstly guess these realm object classes may not woven correctly. But in the build log I find them look like correct.
The part of Build Log:
The full build log file:
buildtest.log
Repro steps
1.Build Project.
2.Got the exception of "no properties in...".
Version
Unity .Net Framework
What Atlas Services are you using?
Local Database only
What type of application is this?
Unity
Client OS and version
Unity2021.3.38f1 & Realm-dotnet 12.0.0
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: