Hi,
My app Walk the World used
- com.magicleap.unitysdk: 2.3.0,
- com.magicleap.mrtk3: 1.1.0
When I released it. All was fine, I saw no reason to update the app, until I tried it just yet. I was a bit surprised that after installing a fresh copy I did not get a permission box. Long story short: Unity’s ARPlaneManager didn’t work anymore, and neither did, apparently, ARMeshManager. After trying a lot of things, it finally occurred to me to updated the SDK to 2.6.0 and the MRTK to 1.4.0 and hey, presto everything worked. Apparently, in the time frame between July 27th and today, the OS update (I am now on 1.12.0) broke something, and the SDK and the OS need to be in sync.
However, I wish to stress this is not a good thing to happen. Devices need to be backwards compatible with apps, especially now since the OS updater can now update OTA and devices can get updated more or less automatically. If a surgeon uses an ML2 in an operating room, the device is updated either automatically or by the IT dept, important functionality cannot break willy-nilly. Apps that worked, should still be working, even after an update. Things can always go wrong, stercus accidit, but not things that are as obvious as this.
For the record: no harm done, this was just my private app Walk the World, it’s updated without changing code, and it works again. But please be careful with things like this, or issue a warning this might happen. If that was issued and I missed it: my bad