Is Xamarin code intentionally using FileNotFoundExceptions to help create the dynamic code adaptability to the various devices and platform versions that the resulting build can support?
When looking at diagnostic output during run time to debug a different problem, I saw numerous FileNotFoundExceptions which don't seem to have any impact on execution. Subsequently, I set the debug settings to break on occurrence to see more details, however was able to continue execution after the break. I even went back to earlier versions of my code and saw the same pattern. Hence the question.