Bug XCode can not build UnityWebRequest.o

Hi

ld: b(l) ARM64 branch out of range (136049796 max is +/-128MB): from +[UnityURLRequest storeRequest:taskID:] (0x00006F60) to __Unwind_Resume@0x00000000 (0x081C64D0) in ‘+[UnityURLRequest storeRequest:taskID:]’ from /Users/xxx/Library/Developer/Xcode/DerivedData/Unity-iPhone-axjxbqexywgtvtcndrhyokjjgstl/Build/Intermediates.noindex/Unity-iPhone.build/Debug-iphoneos/UnityFramework.build/Objects-normal/arm64/UnityWebRequest.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Unity 2020.2.4f1

How can we workaround this?
I even dont know where to start

 

Android easily builded and sizes are:
- libil2cpp.so 311 MB
- managed dlls 24 MB
- il2cppOutput 1228 MB

I dont know exactly is it too much or not. il2cpp always been x50 to managed Code
If this is too much, how can we understand why il2cpp create so much code from such small codebase?

 

Yes we are

Actually nothing changed in xcode project just build.
Will try to find some useful settings.

 

Thanks. We already on google play store, use android app bundles and play asset delivery

Now trying to build for iOS.
Builds stop building few days ago.

Can you please clarify what average ilbil2cpp.so and il2cppOutput size considered normal?

 

@JoshPeterson
Hi, I am having the same problem right now.
And it is not caused by a change in the code, but by a Unity version upgrade. (2020.3.18 -> 2020.3.42)
My project is already released, so it is difficult to raise it to 2021. And I want to use the bug fixes that came in 2020.3.26.
Do you know up to which version I can raise it?
Also, like myself, there are people who say that it occurred when they raised it to 2020.3.33.
This comment section.
https://issuetracker.unity3d.com/is...lding-development-build-with-script-debugging

 

Same here after updating 2021.3.12f1 to 2021.3.15f1

"Strip engine code" is disabled on both versions of Unity, 2021.3.12f1 builds fine, 2021.3.15f1 crashes with the same error above. Enabling "strip engine code" on Unity 2021.3.15f1 fixes the issue.

 

Additional information.
In my environment, "Strip engine code" is enabled and "strippingLevel" is set to Medium, but with 2020.3.42, I get an error.
If I set "strippingLevel" to High, the build passes, but looking at the size of the C++ code, I think this too will soon reach its limit.

 

Oops, my bad.
I always turn off ScriptDebugging.
But doesn't this mean that the C++ code on the Engine side has increased significantly recently?

 

Do you need a full log?
It looks like the same log as when it goes through normally until just before this.

❌  ld: b(l) ARM64 branch out of range (134537264 max is +/-128MB): from +[UnityURLRequest storeRequest:taskID:] (0x00006DA0) to __Unwind_Resume@0x00000000 (0x08054E8C) in '+[UnityURLRequest storeRequest:taskID:]' from /Users/oinkun/Library/Developer/Xcode/DerivedData/Unity-iPhone-ajjzuruupamzzwghesapudcjmrac/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/IntermediateBuildFilesPath/Unity-iPhone.build/Debug-iphoneos/UnityFramework.build/Objects-normal/arm64/UnityWebRequest.o







❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)





** ARCHIVE FAILED **





The following build commands failed:

   Ld /Users/oinkun/Library/Developer/Xcode/DerivedData/Unity-iPhone-ajjzuruupamzzwghesapudcjmrac/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/UnityFramework.framework/UnityFramework normal (in target 'UnityFramework' from project 'Unity-iPhone')

(1 failure)

[08:38:02]: Exit status: 65

 

Yes.
Script Debugging is off.

 

That is an excellent suggestion.
I'll try it tomorrow!
Thanks!

 

This worked perfectly on my project!
Thank you so much!

---

To others who have seen this thread.
IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND is not added to the Unity defines, but to the Xcode defines.
I was using fastlane to build, so I added the following option to xcargs.

```
xcargs += " GCC_PREPROCESSOR_DEFINITIONS=\"$(inherited) IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND=1\""
```

 

Added IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND to xcodebuild and the issue seems to be gone for now.
For those who are building via xcodebuild, the command would look like this:

Code (CSharp):

1. xcodebuild -workspace Unity-iPhone.xcworkspace \
2. ...
3. GCC_PREPROCESSOR_DEFINITIONS='$GCC_PREPROCESSOR_DEFINITIONS IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND=1' \
4. ...
5. -archivePath build.xcarchive archive

 

To others needing to get this working in Unity Cloud Build: I got this working by creating a file called Gymfile in Assets\ucb with the contents :

xcargs 'GCC_PREPROCESSOR_DEFINITIONS="$GCC_PREPROCESSOR_DEFINITIONS IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND=1"'

And a file called ucb_xcode_fastlane.json in Assets with the contents :

{

"gymfile": "Assets/ucb/Gymfile"

}

There was no need to touch any settings in the cloud build settings

 

I cannot get it to work. It seems like the flag got passed fine, but it's not being considered by the build properly or smth


ld: B/BL out of range 182887748 (max +/-128MB) to '__ZN3Geo8GeoArrayIPKN9Enlighten13MaterialGuids12InstanceInfoEE11SetCapacityEi'

clang: error: linker command failed with exit code 1 (use -v to see invocation)

This is the command
xcodebuild -project Unity-iPhone.xcodeproj GCC_PREPROCESSOR_DEFINITIONS='IL2CPP_LARGE_EXECUTABLE_ARM_WORKAROUND=1' -archivePath build.xcarchive archive -scheme "Unity-iPhone"

Unity 2023.1.15f1

 

@JoshPeterson we wanted to bump this thread. We started seeing this exact issue with the macOS Sonoma and Xcode 15 upgrade on our build farm. The builds were working just fine yesterday, and post the upgrades the builds now fail with this issue.

We're currently on 2022.3.11f1 and are seeing the following:

Code (CSharp):

1. d: B/BL out of range 144489060 (max +/-128MB) to '__ZN3Geo8GeoArrayIPKN9Enlighten13MaterialGuids12InstanceInfoEE11SetCapacityEi'

The workaround above does not work, however if you add -ld64 to the other linker flags on the Unity target and framework allows it to build.

Another reference: https://developer.apple.com/forums/thread/738275?login=true&page=1#769744022

Best regards