Couldn't build player because of unsupported data on target platform.

Hi folks,

I am experiencing this problem while building my project.
The build fails with a few messages found in BuildReport:

• Couldn't build player because of unsupported data on target platform.
• Building Player failed
• Building - Failed to write file: globalgamemanagers.assets

Doesn't really look a lot to start with. What makes it a bit more complex is that the same project is build successfully with Cloud build service.

Searching for similar errors didn't yield much, only some legacy GUI related methods failures. Not really applicable to this case imho.

Anyone has experienced this issue with a more recent versions of Unity? I am using 2018.3.8, Android.

 

Backup your project > Remove all folder but keep Assets folder > Try build again.

 

Unfortunately it didn't help.
One more missing bit of info: I build it all in -batchmode.

 

Does it work when building from the Editor?

 

Sure. The complete log file is build.txt and json formatted build messages file is build-messages.txt.
I have removed all sensitive information from the build log file.

 

Yes, absolutely. Builds fine with no related warnings.

 

Please share your build script

 

The script contains some helper classes for arguments, validation and parsing. Those work properly since the provided input data is always correct within the build. The build runs successfully if I build it on another machine.

 

This is what I have tried:

• Windows machine (my PC), Unity Editor Build => OK
• Windows machine (my PC), command line => OK
• Unity Cloud build => OK
• Linux Machine 1 (hosted in cloud), Docker - command line => OK
• Linux Machine 2 (hosted on my PC), Docker - command line => BAD (errors mentioned in post title)

It actually makes no sense to me why would a docker container hosted on a machine A behave different when hosted on a machine B, it is completely isolated and unaware of the host configuration. The docker image is of course the same.

 

The project I work on is commercial.
What are the rules/regulations at Unity regarding this?

 

Sounds good Karl, lets do it then. The project size is 220MB. Let me know the next steps pls.

 

Reviewing the error, "Failed to write file", could it be R/W permissions that might be different between the systems? Just a guess though, but something you might want to check.

 

Bull's eye!
Permissions are the problem. The cloud hosted docker container is spun up using 'docker run' command, locally I use 'docker-compose up'. Although I specify my volumes identically, something still goes wrong with the permissions. And the weird part is that the control over the permissions is not that clear. I was convinced that since I am 'root' in both cases I am almighty to run anything anywhere. It turns out that some file operation within the Unity build fails, not clear why though.. If I do not specify any volumes to mount on the host (from container to my PC) I am safe, it builds fine.
I believe there is no bug here just not a very clear message in the log.
@karl_jones indeed a more informative exception message would be handy.

I will report the message-related issue.
Everyone involved, thanks for the help in the investigation!