Packaged game (debug/development) crashes on startup

Development Platform & Builds Debugging, Optimization, & Profiling
, , , , ,
1

Hello,

This is the first time I’m trying to package my game, and it seems like the debug and development configurations build a packaged game that crashes on startup. The logs are attached: Debug/Development, and since I have no other information, a screenshot: ![Error3.

If there’s anything I can do to get more information on this for you, please let me know, and as always, any help is appreciated!

2

Hi MkII,

Were you ever able to package your project before? Are you running source or binary/launcher?

This may be a known issue, but I do want you to try one thing before I declare it’s the issue (which luckily should make it into a potential hotfix):

In the Engine folder, delete the DDC
(Derived Data Cache).
In your project,
delete the Intermediate, the Saved,
and the Binary folders.

When you next try to package it will take considerably longer as the shaders will need to newly compile, but this should get rid of any old or corrupted files that haven’t gotten deleted.

Thanks!

3

Hi wittlief,

This is the first time I’m packaging my game - I tried briefly in 4.7 but ran into packaging errors so never got to a fully packaged game. In 4.8 these were resolved, allowing me to test the package result.

I will try your suggestion tomorrow and get right back to you. Thanks :slight_smile:

Edit: Also, I’m running 4.8 off of the launcher download, not compiling from source.

4

So I tried as you suggested, and the debuggame and development configurations still exhibit the problem.

5

Ok, on which device are you testing? Can you get logcat logs for the device? If you can run the app long enough so that it catches the crash a number of times that would be the most help.

Thanks!

6

Oh sorry! I didn’t mention I’m packaging for Windows 64bit, not Android (logcat is an Android thing, right?)

I’m going to try the new 4.8.1 update, since the release notes mention:

“UE-17087 Assertion failed: !Result || Result->LinkerLoad == Linker crash”

which I think is related to this since that error message is very familiar (it seems it wasn’t on the screenshot, maybe I forgot to include the debug symbols with the package?)

I will let you know how it goes. Thanks!

7

Good news! It seems 4.8.1 solves my problem. Thank you for your time!