Script Call Optimization on iOS

Hello. I'm new here and we (me and a friend of mine) are working on our very first game to be realized in a couple of months. Our main target platform is iOS (iPhone and iPad). Reading through Unity Documentation there are a couple of stuff I couldn't quite understand, so we would appreciate if you could share your experience/knowledge:

On iOS Player Settings page it says:

• When using the Fast but no Exceptions option, any exceptions that occur will crash the game, and no stack trace will be provided.
• There is no performance benefit with the Fast but no Exceptions option when using the IL2CPP scripting backend.
• When releasing your game to the world, it’s best to publish with the Fast but no Exceptions option.

So when there is no performance benefit in using Fast but no Exceptions option with IL2CPP (which is your only option, as "Mono2x builds are no longer accepted in the App store") and your game will crash upon every exception, why are we recommended to use Fast but no Exceptions option when releasing the game?

Thanks in advance for your contribution.

 

Bumping this for you because I would also like an answer. It does seem like the docs are saying we should use 'Fast but no Exceptions' even though it's providing no benefit at all.

 

I use Fast but no Exceptions because I want my game to crash immediately rather than continue in an undefined state. I use the performance reporting tool to view these unhandled exceptions.

 

I appreciate your response. It is very helpful to get to know that.

Thanks for support.