Console Log 0438.txt
Can you please try this workaround and let me know if it works:
Let me know!
Hello. This fix worked for me. Thanks.
I'm glad the workaround worked for you!
Normally, this is an operation that should be automated by Odin during build.
I'm not sure why it didn't happen automatically in your case.
Without more information about your Unity version or setup, I can't help reproduce the issue.
If anyone else encounters this bug reliably, please comment with your version info and reproduction steps!
Same errors on my side using the Unity / Addressables / Build / Build Player Content (iOS).Checking Any Platform don't resolve the problem.
Ludiq + Bolt + Peek up to dateUnity 2019.3.0b7
Are you getting the exact same errors, or anything slightly different?
If they are the exact same, then the platform enable fix should have worked.
Please send us the log if possible!
I modified the settings (any platform)
I get that errors :
Please uncheck the "Exclude Platform" settings you have checked, except for "Editor". You're effectively excluding your target platform.
Ok. It works. Checking the "any plateform" automatically check "Editor, Standalone, iOS".Resolved to uncheck Standalone and iOs.Many thx
I'm merging your issue with another similar report with a known workaround.
The issue here is that somehow, Odin's build automation script does not automatically kick in and set the right platforms for your current build target, which makes builds fail because the Odin attributes are not found.
This is why manually fixing the Odin DLL importer settings as indicated by the workaround above fixes it.
However, I can't get it to reproduce here at all. The Odin automation build always kicks in and sets the proper targets in the importer settings, even if I purposely uncheck/remove it beforehand.
Here's a test of me building for Peek + Android + IL2CPP + Unity 2019.3:
Unless anyone has clear reproduction steps, I can't help any more in debugging this so I'll have to mark this as cannot reproduce.
Hopefully people faced with the same issue can post repro steps, but otherwise the workaround seems to work for everyone.
Customer support service by UserEcho