x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

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 :(

Product Version: UE 4.18
Tags:
more ▼

asked Dec 24 '17 at 05:40 AM in Bug Reports

avatar image

PantherNZ
66 5 7 15

(comments are locked)
10|2000 characters needed characters left

2 answers: sort voted first

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 =\

more ▼

answered Jan 07 '18 at 02:10 AM

avatar image

PantherNZ
66 5 7 15

(comments are locked)
10|2000 characters needed characters left

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?

more ▼

answered Dec 24 '17 at 06:36 AM

avatar image

Jin_VE
4.4k 31 77 40

avatar image Jin_VE Dec 24 '17 at 06:37 AM

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.

avatar image PantherNZ Dec 24 '17 at 11:46 PM

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

avatar image Jin_VE Dec 25 '17 at 04:08 AM

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.

(comments are locked)
10|2000 characters needed characters left
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question