Using the iOS builder for Windows asset I tried building an iOS project.
However, the tool is returning an error that the IL2CPP build is failing due to a dag file being unable to be loaded.
Apparently Unity 6 is handling something different in IL2CPP which causes this error.
The author cannot do anything because it is not in his domain to fix and says that Unity should fix it.
Knowing QA, they’ll say that iOS building on Windows is not supported. The author believes that the tools is being used by Unity themselves internally.
So is there any staff that could take a look at this?
Even though it is actually not officially supported.
To build for iOS, you need a macOS.
This is more a legal restriction than a software one.
There is a legal section from docs of iOS Builder:
In the license that comes with the iOS SDK, Apple Inc. states that the iOS SDK shall only be deployed on Apple-branded computers. So, for the rest of this document, I will assume that your Windows computer is an Apple-branded computer running Windows through Boot Camp. I do not condone the use of this program outside this scope, and cannot be held responsible for any misuse you make of it.
As explained, the dev of the iOS Builder for Windows asset cannot do anything about it because it is only in Unity’s power to fix.
Yes I know, yet people work around it. Just because apple does not provide a way to build on Windows, forcing developers to buy a mac or find other ways of dealing with it.
It’s just cumbersome to have a mac around you at all times. Especially when working from home. Not every company has spare macs available.
When I am about to release the product I do build with a mac and upload it to the store that way. But for bug fixing I use this tool to quickly make builds when working from home.
Yeah the macs that we do have are in use. Remote building is not available then.
Not to mention you’d have to build and export the ipa every time.
I’m not going to discuss why I’m using this asset. I’m just asking whether a Unity staff could have a look at it. Since the author says that it is being used by unity internally.
If it won’t be fixed, it won’t be fixed then that is final.