# "PackagingResults:Error: Error Launch failed! Unknown Error" when trying to build for Android VR

**URL:** <https://forums.unrealengine.com/t/packagingresults-error-launch-failed-unknown-error-when-trying-to-build-for-android-vr/426226>\
**Category:** Mobile\
**Tags:** google-cardboard, Daydream, unreal-engine, packaging-projects, UE4, question\
**Created:** [May 29, 2018, 7:13pm UTC](https://forums.unrealengine.com/t/packagingresults-error-launch-failed-unknown-error-when-trying-to-build-for-android-vr/426226 "2018-05-29T19:13:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_621169c1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_621169c1](https://forums.unrealengine.com/u/anonymous_user_621169c1)\
**Post date:** [May 29, 2018, 7:13pm UTC](https://forums.unrealengine.com/t/packagingresults-error-launch-failed-unknown-error-when-trying-to-build-for-android-vr/426226/1 "2018-05-29T19:13:05Z")

</div>

Hi there

I’m currently trying to build a test level for Android VR (Google Cardboard + Daydream) and I’m having trouble either packaging the project or deploying it to my phone via USB debugging. I’m getting an “Unknown Error” as well as " AutomationTool exiting with ExitCode=5 (5)"

Here’s a pastebin link to my output log: [https://pastebin.com/Ren1Fbsp](https://pastebin.com/Ren1Fbsp)

Any help would be greatly appreciated! Thank you!

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_621169c1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_621169c1](https://forums.unrealengine.com/u/anonymous_user_621169c1)\
**Post date:** [May 29, 2018, 7:21pm UTC](https://forums.unrealengine.com/t/packagingresults-error-launch-failed-unknown-error-when-trying-to-build-for-android-vr/426226/2 "2018-05-29T19:21:14Z")

</div>

Never mind, I think I fixed it!  
For anyone with the same question, I had support for both 32 and 64 bit ARM selected, which seems to break it. Leaving this question up to hopefully help anyone with the same issue.
