incompatibleFeatureTypes for Quest features #15

Ideally we'd have a single build for all android devices. We are tantalisingly close so it's slightly disheartening to see this:

Can you explain in more detail exactly what is incompatible? What the effects are (maybe they are tolerable or can be mitigated)?

Is there a way to have runtime guards that solve the incompatibility and thus can coexist in the same build?

Is this maybe best regarded as a bug in the Quest SDK that needs to be reported (making the defensive code at least potentially temporary)