XR_EXT_UUID makes spatial anchors unsupported on Quest3 in XR (fix available)

Encountered problem:

commit: 11503161090f81b690c1682266478be29ce3feff 

Made on Jan 26 by lagocs 

This commit introduced the extra requirement for XR_EXT_UUID_EXTENSION_NAME inside OpenXRSpaceExtension.cpp

However this is not a supported extension for the Quest3 as I have found out (on firmware 0.62 and 0.63, I cannot comment on prior firmwares as I cannot downgrade my quest3 firmware). This made m_spaceExtensionSupported allways false.

Now if you still loaded the SpatialAnchorModel component in QML you would witness a crash (try it). That crash is a bit strange as it should be guarded against but oh well, not that important right now. 

Confirmed Solution :

By commenting this line 85:

It will resolve m_spaceExtensionSupported as true and everything will work as normal  

NOTE: make sure your app has spatial permissions inside the quest3, just putting the permission request in the android manifest was not enough for me. Whether the quest OS is throttling the permission requests I don't know but to be sure go to Privacy->spatial permissions and manually go to your installed app to enable the permission