iOS Build Environment Help Center
• Windows 11
• 3.62
• 17.4
• When building I'm getting this error, I've tried to look for similar but didn't find anything.
This build was with LLVM off and try to fix unresolved symbols On.
I've tried to supply the builder with the frameworks but it also didn't work, when I'm using only Ironsource and not unity ads alongside it with mediation it builds correctly.
I'll be sending you the xcode project through e-mail so you can take a look if needed
Hello
Conflicting methods usually mean a problem in the source code.
This looks like a code generation, ie a project error. Does the same Xcode project build on Mac ?
I'll try on a mac later today and tell you what happens, I deleted Ironsource mediation and installed again to make sure it was clean and no conflicts could happen (Since when you update sometimes ironsource leaves duplicated classes)
Let me know if it happens again. If Xcode can build it and the builder can’t it’ll mean I have to do something. Assuming we’re talking about the exact same Xcode project of course.
It indeed built, I only had to do this workaround for Balaso Localizaton in Mac since there is a bug when you build in windows before sending to xcode as it messes the absolute path.
But that's not a problem when using the asset, since the problem lies with using UnityAds from the ironsource mediation; And that built correctly on macos
Workaround for balaso:
https://github.com/Balaso-Software/app-tracking-transparency-for-unity/issues/31
I had sent you the same xcode project I'm using through e-mail if oyu'd like to look
Hello? As mentioned, xcode Can Indeed build it.
Hello
Sorry for the delay. Your problem is a difficult one, and I can't allocate as much time to improve this builder as I wish I could. Additionally, when I spot easier problem reports on the forum it happens that I answer them before completing yours, to not let everyone wait.
I'll keep investigating until I find the solution.
Sorry, I really don't want to bother I just didn't know you were looking into it.
But Basically these problems started when unity and ironsource United.
You may find the solution if you look into using unity mediation with ironsource and unity ads.
Since if you want unity ads today you'll need to use that I believe it's something important to look into.
Thanks
FYI your project built past the link stage without problems with the version of the builder I'm working on and that I'm about to release very soon (v3.64). The linker used was Apple ld64. What prevented me to complete the build was a missing entitlement in my provisioning profile (the generic provisioning profile that I use to build test case apps doesn't have the Game Center entitlement).
I'm Here to say Thank you! It works and I was finally even able to add the ADQualitySDK too, seems like the days having to downgrade Unity ads by 10+ months are gone.
Thanks for all the work, this is indeed the best asset
Glad to hear that everything is working as intended :-)
Moderators: Pierre-Marie Baty