What strategies you use to find the
problems in the Log?
First and foremost I open the log with Notepad and not in programs like MS Word. I then make sure that Word Wrap is turned off! This makes the log much more manageable to read and sift through the information without looking very daunting and a muddled mess.
Then I will start by scrolling to the bottom and then back up to where I see any Build Failed errors, same for crash logs too. Depending what is said there I can see where I would go next, whether it’s the UAT log location (which is mentioned typically under the build failed area), or if I could resolve whatever is mentioned there in the Build Failed section.
Looking through this attached log though I’m seeing missing files and redirectors not being found. This stuff will need to be cleaned up likely before you can fully package. You can try using the right-click context menu option for “Fix Up Redirectors” on the content folder in your project and see if that cleans up any issues. You can also try in the Project Settings > Packaging section to set only the maps that need to be packaged instead of building the entire project and all content and maps.
You can also try enabling the option under the same Project Settings > Packaging for “Full Rebuild” if it’s not already. This will rebuild the full package rather than iterating on a previous one that may have outdated content or code that could be causing issues as well.