ViceVersa
January 1, 2021, 5:26am
1
Ever since I updated my project to 4.26.0, the engine has been extremely buggy and crashing all the time. I was able to just save constantly and deal with that, but now packaging for android is no longer working either. Here is the log
UATHelper: Packaging (Android (ASTC)): LogInit: Display: LogOutputDevice: Error: begin: stack for UAT
unit23
January 1, 2021, 10:45am
2
During engine version updates each file is assessed, which then can bring dormant issues to light. Thus, generally version updates do not necessarily mean it is really the new version fault. However, it may be related.
Do you perhaps have any idea where you assigned these package names, or path? If yes, go there and refresh nodes, or even break node connections.
unit23
January 1, 2021, 11:01am
3
Also try this, remove your config files and see if you can cook without it. Perhaps the path is wrongly set somewhere in the config files. Keep packaging settings after checking them for correct paths.
ViceVersa
January 1, 2021, 6:21pm
4
unit23:
During engine version updates each file is assessed, which then can bring dormant issues to light. Thus, generally version updates do not necessarily mean it is really the new version fault. However, it may be related.
Do you perhaps have any idea where you assigned these package names, or path? If yes, go there and refresh nodes, or even break node connections.
I dont know what SoftObjectPath even is… I have no idea what that error is talking about… this is a blueprint project btw
ViceVersa
January 1, 2021, 6:24pm
5
So i tried deleting the build intermediate and config files, then setting everything in the android settings again, but still exact same outcome. I should also add I just did a fresh windows install, and reinstalled unreal 4.26, visual studio, and android studio, same result
ViceVersa
January 1, 2021, 6:53pm
6
Oh i would also like to add to this, I can launch the project on my tablet from the editor and it works fine. Packaging is the only thing causing the issue
unit23
January 1, 2021, 7:14pm
7
Okay that is good. Use the launch button and observe the Output log, are there any red errors?
ViceVersa
January 1, 2021, 8:02pm
8
There were no red errors, it launches perfectly without issue.
unit23
January 1, 2021, 8:09pm
9
ViceVersa:
There were no red errors, it launches perfectly without issue.
The script folder is probably fine, and the drive letter probably is also not relevant. I really can just guess too, but I suggest you disable Event Driven Loader and look again if something pops up in the output log when launching. Also make sure you have debug symbols installed, and if you pack make it DebugGame. Also if this remains inconclusive google for Android unknown error and add snippets of your log and read the AnswerHub entries related to it.
Also if it still remains an issue, try just upgrading to 4.26, perhaps this fixes it or results in better debugging infos. Make sure to always have a project backup. Good luck!
unit23
January 1, 2021, 8:12pm
10
Also Remove this map from the project and see if the issue is still there TopDownExampleMap, or first try to remove this ModelComponent_0.BodySetup_0
unit23
January 1, 2021, 8:14pm
11
Pinging you again, read my second reply above.
ViceVersa
January 1, 2021, 8:36pm
12
well, i deleted the map and made a new one, those original map warnings were gone, though all the red errors seem to persist
UATHelper: Packaging (Android (ASTC)): LogInit: Display: LogOutputDevice: Error: begin: stack for UAT
unit23
January 1, 2021, 8:56pm
13
Google this
Do you perhaps have some file called NoneNoneNone, or is your project name length very short? The error suggests to me that there is some issue with naming something wrongly.
ViceVersa
January 1, 2021, 9:24pm
14
there is nothing called ‘nonenonenone’ and the project name isnt that short? Doest that matter? How long should it be? its 10 letters long, and mind you this was all working before the official release of 4.26.0
IanPlayer
January 3, 2021, 12:49pm
15
um。。。i have met this bug for twice，first time，i take a day to rewrite my blueprint project,and it works.but this time ,i don’t do that anymore .is there anyone can help?..
ViceVersa
January 4, 2021, 4:32am
16
So this problem was caused initially i believe because of unreal crashing, which i was able to fix by reinstalling windows, unreal 4.26, visual studio, and android studio. the problem kept persisting and i was able to boil it down to one blueprint causing the error, for seemingly no reason. I believe a file just got corrupted from the crash as i was able to copy and paste the code, delete the old blueprint, and then the problem stopped.