# Android build not working
**URL:** https://discourse.kitware.com/t/android-build-not-working/899
**Category:** Pulse Physiology Engine
**Created:** [September 26, 2022, 7:06pm UTC](https://discourse.kitware.com/t/android-build-not-working/899 "2022-09-26T19:06:51Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@colevxr](https://discourse.kitware.com/u/colevxr)
#### Post date: [September 26, 2022, 7:06pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/1 "2022-09-26T19:06:51Z")
I’ve been having some issues making a working android build of the vitals monitor using the pulse engine. When I just play it in editor, it works fine.
However, when I try to build to Android, it no longer works. The lines don’t show up and the numbers don’t change. In the android logcat, I get this error.
Does anyone have any suggestions on how to fix this issue?
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [September 26, 2022, 8:33pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/2 "2022-09-26T20:33:14Z")
[This unity release candidate package may have working androd libraries](https://data.kitware.com/#item/62be6cd5bddec9d0c419f63e)
We are going to realse soon, so I will rebuild an asset then.
There are also build instructions on our Pulse engine repo, [but it is a bit of a chore](https://gitlab.kitware.com/physiology/engine/-/blob/4.x/xcompile.bat)
---
### Author:  [@colevxr](https://discourse.kitware.com/u/colevxr)
#### Post date: [September 27, 2022, 3:10pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/3 "2022-09-27T15:10:35Z")
I just tried the package, it doesn’t seem to work.
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [September 27, 2022, 3:35pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/4 "2022-09-27T15:35:32Z")
What kind of android device are you running on?
---
### Author:  [@colevxr](https://discourse.kitware.com/u/colevxr)
#### Post date: [September 27, 2022, 3:59pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/5 "2022-09-27T15:59:37Z")
The Meta Quest
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [September 27, 2022, 4:01pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/6 "2022-09-27T16:01:10Z")
I believe we may need to build against the meta quest SDK… but I am not sure.
The android binaries are build against the standard android sdk, which may or may not be what the quest wants…
---
### Author:  [@colevxr](https://discourse.kitware.com/u/colevxr)
#### Post date: [September 29, 2022, 9:09pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/7 "2022-09-29T21:09:10Z")
Is there anything I can do?
---
### Author:  [@abray](https://discourse.kitware.com/u/abray)
#### Post date: [October 4, 2022, 3:41pm UTC](https://discourse.kitware.com/t/android-build-not-working/899/8 "2022-10-04T15:41:39Z")
Download the meta quest SDK and build Pulse per its requirements.
I had to do the same thing to get [Pulse to run on the Magic Leap](https://gitlab.kitware.com/physiology/engine/-/tree/4.x/#magic-leap)
I have not done any investigation with meta to see how similar/easy/hard this is
---
### Author:  [@aleksandr.sharshakov](https://discourse.kitware.com/u/aleksandr.sharshakov)
#### Post date: [August 29, 2023, 8:02am UTC](https://discourse.kitware.com/t/android-build-not-working/899/9 "2023-08-29T08:02:53Z")
Hey,
I totally get how frustrating it can be when things work perfectly in the editor but throw a tantrum on Android builds…
I’ve had my fair share of Android build woes, especially when dealing with specialized engines like the pulse engine (those were the days of working on projects at [Andersen](https://andersenlab.com/)). It sounds like you’re running into a compatibility hiccup between the engine and Android. The error in your logcat might be pointing towards a compatibility or resource issue.
One thing you could try is downloading the MetaQuest SDK and building Pulse based on its requirements. Sometimes these specialized SDKs have specific optimizations for Android that can make all the difference. Also, ensure that your project settings are aligned with Android build configurations, and that all necessary assets and dependencies are packaged correctly.
Remember, it’s a bit of trial and error, so don’t get disheartened. We’ve all been there! Keep experimenting, diving into relevant forums, and seeking guidance. You got this!