View Issue Details

IDProjectCategoryView StatusLast Update
00295832.x IDE BugsBuild AndroidPublic2019-01-04 16:04
ReporterStewart BishopAssigned ToDan 
PriorityMediumSeverityC - GeneralReproducibility100%
Status ClosedResolutionFixed 
PlatformAndroidOSWindows 10OS Version
Product Version2.2.0 
Target Version2.2.1Fixed in Version2.2.1 
Summary0029583: Build Android: Building for an architecture your NDK doesn't support doesn't stop your build from happening
DescriptionWith the release of the latest NDK you are no longer able to build for MIPS or Armv5, these are still able to be selected in the IDE if the user chooses to use an older NDK for some reason. If you build for a device which requires Armv5 according to our architecture check then you're required to select this in your game options to build otherwise it'll not continue, assuming you do a YYC build then the first architecture it will build will be Armv5 and it will continue until the NDK tries to find files specific to this and then instantly fails.

Expected would be that we do a check to see what versions your NDK supports and then compare that against what architectures you've specified in game options and then stop your build before it can happen so users aren't wasting their time.
Steps To Reproduce1) Set your NDK to the latest
2) Set armv5 as one of the platforms to build
3) Run an android YYC build
4) See that this fails as it doesn't exist anymore
Tags221, AmazonFire, android, Build, IDE
2.x IDE Found In2.2.0.301
2.x Runtime Found In2.2.0.222
2.x IDE Verified In
2.x Runtime Verified In2.2.1.287

Relationships

related to 0029582 ClosedRussell Kay Build Android: Architecture check still happens even if your device is not connected, results in incorrect ARMv5 error 

Activities

Dan

2018-12-06 16:26

Adminstrator   ~0062183

No longer required, as 2.2.1 removed the invalid architectures and we have another report in that a run should confirm the architecture of the device before starting the build and a Create shouldn't check until installation and then just skip if the architecture doesn't match, so the remaining work here is superseded by that other report.