Is it possible to prevent AssertionComponent from being stripped out of non-dev builds?

I’d like to use the AssertionComponent to do some automated testing and have the tests run on actual devices. Everything that I’m trying to do works great in a dev build, but part of my company’s normal workflow is to run all of our automated tests on non-dev builds. Is it possible to prevent the AssertionComponent from being stripped out off of game objects in a release build?

Yes, please look at the AssertionStripper.cs file/class and modify as needed.