# Can't launch APK on Android

**URL:** <https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390>\
**Category:** Mobile\
**Tags:** unreal-engine, Android\
**Created:** [June 21, 2023, 3:32pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390 "2023-06-21T15:32:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Batoosai47](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Batoosai47](https://forums.unrealengine.com/u/Batoosai47)\
**Post date:** [June 21, 2023, 3:32pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390/1 "2023-06-21T15:32:00Z")

</div>

Hello,  
I’m starting UE 5.2 , i was trying it with windows projects 1 week ago and loved it,now i want to create an Android App but first of all i wanted to check if i can even compil a project and run it on my android device (or bluestack) what a good idea,i’m stuck with that problem since 2 days,checking all tutos on the internet,scratch install,another computer,but still can’t launch an empty map with just the started point . . .

**Version : Unreal Engine 5.2 windows 10 x64**

**Android studios Flamingo 2022.2.1 Patch 2(latest)**

- APIs : 34/ 12LSv2/ 12.0(S) / 11.0(R) / 10.0(Q) /8.0 (Oreo) / 7.1.1 (Nougat)
- SDK Build Tools : 34 / 33.0.2 / 32 / 31 / 30.0.3/ 30 / 29.0.3 / 29.0.2 / 29.0.1 / 29 / 26.0.3 / 25.0.3
- NDK (side by side) : 25.1.xxx
- Android command line tools : 8.0
- CMake : 3.10.2
- Android SDK platform Tools : 34.0.3
- Visual Studios 2022
- Testing Devices : Android Samsung Galaxy M13 USB Devs mod (physic); Android version 13 /UICore 5.1
- Bluestack Android emulator : Android 11 / PIE 64 / Nougat 64.
- Android Studio Emulator : Android 13 Tiramisux86\_64 / API 33  
**Testing Method** : .bat in project / Drag and drop .apk / from UE 5.2 (plateform/mydevice) all failed.

**Unreal Engine Project Settings :**

 ![ue5settingpro](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/3/a/23a1e81790d38813e91f76f84f9ee9cc5a3a1cde.png)  
 ![ue5settingpro2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/a/4/2a43885d4dd8a10b879f3813ce96a51a91e153ba.png)  
 ![ue5settingpro3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/3/5/b35ed0984f5305403c96a3a17ed295b12e53e4a8.png)  
 ![ue5settingpro4](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/f/1/bf1689fef12d67284069fde5c555fd4b6dcba4f2.png)

**Tests and Errors in an empty Mobile project with just a started point (No light,No ground,Nothing…):**  
**Samsung :**

- UE 5 .2 Package Project Ok / Drag and drop computer to device : Install Ok / Launch Ok screen freezing on Unreal Engine screen, nothing happen.
- UE 5.2 Quick Launch : Failed :

**LogPlayLevel: Error: UAT: ERROR: Installation of apk ‘C:\Users\RELOAD GAMING BAR\Documents\Unreal Projects\MyProject\Binaries\Android\MyProject-Android-Shipping-arm64.apk’ failed: [INSTALL\_FAILED\_NO\_MATCHING\_ABIS: INSTALL\_FAILED\_NO\_MATCHING\_ABIS: Failed to extract native libraries, res=-113]**  
LogPlayLevel: UAT: Performing Streamed Install  
LogPlayLevel: UAT: (see C:\Users\RELOAD GAMING BAR\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE\_5.2\Log.txt for full exception trace)  
LogPlayLevel: UAT: AutomationTool executed for 0h 0m 39s  
LogPlayLevel: UAT: AutomationTool exiting with ExitCode=35 (Error\_AppInstallFailed)  
LogPlayLevel: Completed Launch On Stage: Deploy Task, Time: 26.023316  
LogPlayLevel: UAT: BUILD FAILED  
**PackagingResults: Error: Launch failed! Failed to Install app**

On bluestack for PIE x64 & Android 11, Got : this device only supports OpenGL ES 2/3/3.1 which is not supported only support ES 3.2+  
On Android Studio :

 ![AndroidStuError](https://d3kjluh73b9h9o.cloudfront.net/original/4X/5/5/e/55eb4350361e8b80d510715c192fd65412b09d6a.png)

I tryed All tutos on the net and i dont know how to Launch an Apply made with UE 5.2 i run out of ideas . . .  
Please someone to unlock my situation, i’m desperate 😭  
Thank you

---

<div class="post-metadata">

**Author:** ![junaidmohammadk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@junaidmohammadk](https://forums.unrealengine.com/u/junaidmohammadk)\
**Post date:** [November 29, 2023, 5:23pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390/2 "2023-11-29T17:23:40Z")

</div>

Did you resolved this issue? because i am facing the same

---

<div class="post-metadata">

**Author:** ![Bikontop](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Bikontop](https://forums.unrealengine.com/u/Bikontop)\
**Post date:** [May 20, 2024, 5:37pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390/3 "2024-05-20T17:37:48Z")

</div>

Did you resolved this issue? because i am facing the same

---

<div class="post-metadata">

**Author:** ![raianlp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@raianlp](https://forums.unrealengine.com/u/raianlp)\
**Post date:** [May 22, 2024, 10:17pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390/4 "2024-05-22T22:17:38Z")

</div>

Don’t do Quick Launch. It is really not working well in UE5+. Use Project Launcher instead. Works like a charm!

---

<div class="post-metadata">

**Author:** ![OddCash4819](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@OddCash4819](https://forums.unrealengine.com/u/OddCash4819)\
**Post date:** [September 22, 2026, 4:19pm UTC](https://forums.unrealengine.com/t/cant-launch-apk-on-android/1206390/5 "2026-09-22T16:19:02Z")

</div>

With UE 5.2, I’d double-check that the Android SDK/NDK versions match the versions officially supported by that UE release rather than simply using the newest Android Studio components. In particular, the NDK and SDK configuration can cause packaging/deployment failures even when everything appears installed correctly.

I’d also try packaging a Development build and check the Output Log for the first actual Android/Gradle error. That should narrow it down much faster than repeatedly reinstalling everything.
