Android SDK 37, with NDK 30 (release candidate), won't parse properly - it saves as platforms/android-37.0, while the current code expects SDK versions to always be u32. As a result, when NDK 30 goes out of release candidate, this will be broken on the most up-to-date SDK + NDK pair.
I haven't tested the 30 NDK directly, I noticed this when messing with platform tools it didn't yet support, but in general this may become a bigger problem soon.
Android SDK 37, with NDK 30 (release candidate), won't parse properly - it saves as
platforms/android-37.0, while the current code expects SDK versions to always be u32. As a result, when NDK 30 goes out of release candidate, this will be broken on the most up-to-date SDK + NDK pair.I haven't tested the 30 NDK directly, I noticed this when messing with platform tools it didn't yet support, but in general this may become a bigger problem soon.