Android build not working

Pulse Physiology Engine
1

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.

image
image1920×1080 378 KB

Does anyone have any suggestions on how to fix this issue?

2

This unity release candidate package may have working androd libraries

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

3

I just tried the package, it doesn’t seem to work.

4

What kind of android device are you running on?

5

The Meta Quest

6

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…

7

Is there anything I can do?

8

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
I have not done any investigation with meta to see how similar/easy/hard this is

9

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). 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!