Android Project crashes on startup in 4.18.2

Hello, I recently upgraded from 4.17.2 to 4.1.8.2. I built my project as usual for Android ETC1 to test it. It installs correctly on my device but crashes after displaying the splash screen when I launch it. I used logcat to try see what happens and it appears to fail on the following assert:

[2017.12.23-01.18.57:044][  0]Assertion failed: Enclosing block should never be called [File:D:\Build\++UE4+Release-4.18+Compile\Sync\Engine\Plugins\Runtime\AndroidDeviceProfileSelector\Source\AndroidDeviceProfileSelector\Private\AndroidDeviceProfileSelectorModule.cpp] [Line: 22] 
12-23 14:18:57.045 13625 13653 D UE4     : 
12-23 14:18:57.045 13625 13653 I art     : System.exit called, status: 0

Why is this assert even occurring on a packaged build? Is that what is even causing the crash?

I can upload the full logcat if it helps. Anyone else had this issue? Is this something on my end? Would be great if I could upload between a version one day and not have 500 issues :frowning:

Here is the code that is failing (the checkNoEntry() line specifically):

const FString FAndroidDeviceProfileSelectorModule::GetRuntimeDeviceProfileName()
{
	// We are not expecting this module to have GetRuntimeDeviceProfileName called directly.
	// Android ProfileSelectorModule runtime is now in FAndroidDeviceProfileSelectorRuntimeModule.
	// Use GetDeviceProfileName.
	checkNoEntry();
	return FString();
}

It looks like AndroidProfileSelectorModule has been changed. FAndroidDeviceProfileSelectorRuntimeModule is the new deal. Not sure about specifics but do you recognize it?

Seems you might be calling GetRuntimeDeviceProfileName() but they want you to change that to GetDeviceProfileName(). Or maybe use this other module class, it’s hard to tell without more info.

It appears to be a bug in the engine somewhere then that still uses this? None of my code calls any of this stuff =\

Try disabling the plugin. Perhaps it isn’t required for your project. Or, the errors might show you where you are using it. I did a quick search of the source and nothing in there appears to use it.

Well I have fixed this issue by disabling the Android Device Profile Selector plugin but I certainly don’t think it is the most optimal solution =\