5.2.1 Android Not Producing Logs

[RealAero]

I am noticing on 5.2.1, if you select project default for Binary Configuration, its builds shipping no matter what you have selected in project settings.

Also I am noticing, if I click Development manually, the app doesn’t produce logs! What gives?!

I know its development because the quad screen tap opens the console, but there is no log left in my device!!

Also using the Launch feature doesn’t work anymore. When the process is complete, the actual Launch command doesn’t make the phone do anything.

Android support appears to be deteriorating.

[leehammoud]

Did you figure this out? Having same issue with it not producing logs

[RealAero]

This is a very annoying temporary fix:

How to get Android Logs with Scoped Storage?

Alright, this is not what we want to see, but it will do for now. Thank you to lion from Multiplayscape with providing me with a solution. You do need to use a source build, I already am so it’s not too bad, but definitely will be a bummer for those on binary. Also you will need to rebuild the engine which takes time. In the file: UnrealEngine\Engine\Source\Runtime\Core\Private\Android\AndroidPlatformMisc.cpp Comment out lines 290 and 321. (Add // before the line.) [image] Make sure to ma…

[briekeMVI]

This temporary fix isn’t exactly a fix. If you select ‘For Distribution’ or from what I’m reading in the original post setting binary configuration will flag the build as UE_BUILD_SHIPPING which seems completely incorrect to me. Is there some way to ensure that builds don’t get configured as shipping simply because ‘For Distribution’ is checked?

[RealAero]

@briekeMVI

This temporary fix isn’t exactly a fix. If you select ‘For Distribution’ or from what I’m reading in the original post setting binary configuration will flag the build as UE_BUILD_SHIPPING which seems co

From what I understand, all “For Distribution” does is force the build to be set to shipping

[briekeMVI]

Previously “For Distribution” would sign the built apk only. If you have previously installed versions of an application installed on the device the signatures need to match.
Now checking “For Distribution” also forces a shipping build which eliminates all logs, and not ideal. I would hope for some sort of flag to enable application signing without forcing the build into Shipping mode.

[brickelstone (Picoworkers)]

Issue: Binary Configuration Defaulting to Shipping

• Solution: Explicitly select “Development” or “Debug” instead of “Project Default” to avoid unintended shipping builds.

Issue: No Logs in Development Build

• Solution: Ensure logging settings in DefaultEngine.ini:

ini

LogConsoleResponse=all
LogWindows=all

Issue: Launch Feature Not Working

• Solution: Verify device connection, check for errors in Output Log, ensure correct platform SDK, and try manual deployment if needed.

For further assistance, refer to Unreal Engine documentation or contact Epic Games support.

[briekeMVI]

@brickelstone

Solution: Explicitly select “Development” or “Debug” instead of “Project Default” to avoid unintended shipping builds.

This is incorrect. If you mark a build as “For Distribution” Unreal 5.2 will force the build Shipping and all logs are stripped.

[briekeMVI]

The real answer is to comment out this if statement
https://github.com/EpicGames/UnrealEngine/blob/ed1fb28a68554f739f91a9e0080e73365d12d842/Engine/Source/Editor/TurnkeySupport/Private/TurnkeySupportModule.cpp#L484
And simply remove the ternary operator from this line to have it just set the configuration
https://github.com/EpicGames/UnrealEngine/blob/ed1fb28a68554f739f91a9e0080e73365d12d842/Engine/Source/Editor/TurnkeySupport/Private/TurnkeySupportModule.cpp#L589