When an exception occurs in managed code, the stack trace for the exception can help you understand the cause of the exception. However, the managed stack trace might not appear as expected for some cases on iOS. The stack trace also varies depending on the Xcode build configuration.
When you use the debug build configuration with iOS, IL2CPPA Unity-developed scripting back-end which you can use as an alternative to Mono when building projects for some platforms. More info
See in Glossary will report a reliable managed stack trace, and include each managed method in the call stack. The stack trace doesn’t include line numbers from the original C# source code.
When you use a release build configuration, IL2CPP might produce a call stack that’s missing one or more managed methods. This is because the C++ compiler has inlined the missing methods. Method inlining is usually good for performance at runtime, but it can make call stacks more difficult to understand. IL2CPP always provides at least one managed method on the call stack. This is the method where the exception occurred. It also includes other methods if they’re not inlined.
If you can reproduce an exception locally, use Xcode to find inlined methods. Run the application in Xcode, using the release configuration, and set an exception breakpoint. The native call stack view in Xcode will indicate which methods actually exist, and which have been inlined.
IL2CPP call stacks don’t include source code line number information by default in debug or release configurations. You can enable source code line numbers using the following steps:
Note: Using this option can increase both the build time and final size of the built program.