Hey everyone,
In case anyone was wondering, I managed to package with UE 5.4 using the steps in this guide.
The app runs and seems to be stable.
The only hiccup is that the virtual keyboard does not appear when clicking a text box (on a quest 2). Not sure what causes the this as I never had this issue before.
Any ideas?
@antinnit
I did post about the Virtual Keyboard issue with a solution a few versions ago, its a bug in Unreal and the workaround is fun: Virtual Keyboard Quest 2, UE5.1 - #7 by ssamevanss
Iâve not used this workaround in awhile as it keyboard on Quest is so bad I rolled my own that doesnât require typing as an input.
I did already have the manifestoverride in place.
I donât have Requires system keyboard enabled for 5.3.2 and yet the packaged app has the virtual keyboard
I guess Iâll have to wait for the MetaXR plugin for 5.4.
Thanks for the info nonetheless!
For me this SetupAndroid.bat error was fixed by:
Hi Iâm running into an issue where i am able to build and package the vr template project into my meta quest pro without a problem. However, when I run vr preview on my computer with live link enabled, it doesnât seem to connect to the live link. I can hear audio but it renders the vr preview as though it were on the desktop rather than rendering it virtual space in my headset. For reference this is what I see in vr:
Why does all the studio tools take up 96gb of hard drive space. That is so much bloat. Is there a bare minimum install much smaller?
just a note, I did a full clean Windows install and did exactly as mentioned here, and I got a fail in the andriod.bat file on the UE5 to install directory, and when building an APK I ran into an unknown build error, without an error code.
the failure on the andriod.bat file is
Warning: Errors during XML parse:
Warning: Additionally, the fallback loader failed to parse the XML.
everything else was a success.
and the build error was,
that I copied the MetaXR and MetaXRPlatform plugins into the UE5 installed plugins folder which led me to the unknown error,
Once I put those plugins into the Project folder that I created the build was a success.
so can someone tell me what that XML parse error is and why canât I put those 2 plugins into the UE5 install location so that I donât have to copy them to the project folder every time I create a project?
Hi
I would like to share with you my experience
Iâm on windows 11.
I have followed this great tuto, but unfortunately, it didnât work for me
Everytime I have messages error when I launch SDKmanager.bat (Error during XML Parse) and it was not possible to package in 5.3.
After lots of hours to follow tutos and be lost in various ways, I have tried this solution:
Uninstall Android studio and clean all android files:
Install Android again:
https://www.youtube.com/watch?v=ypR_YsnJaJo
I have ticked all command line tools as mentionned in the video
and selected:
Under the âSDK Platformâ tab Tick: Android API 34, Android 12L (Sv2)
I donât ticked this one: Android SDK Build-Tools 35-rc2"
Tick the boxes for: 34.0.0. 33.0.1
Tick the box next to: 25.1.8937393
Then I have restarted my PC
I have cleaned all environment variables mentionned in the vidéo: ANDROID_HOME, JAVA HOME, SDK ROOT ET NDK ROOT
and launch sdkmanager.bat. There were XML PARSE errors, but updates were done
I didnât need to accept licences, (I donât know why)
All environment variables were created automatically
And my package was exported succesfully
Sounds like the issue was a messy Android SDK install. A full uninstall, clearing environment variables, and reinstalling can help if sdkmanager.bat throws errors (also checking for updates in Android Studio). Thanks for the fallback for when issues pop up!
Hello,
I have started to use the Quest 3. I just used the default XR Plugin and was Anke to use everything in the vr Template also when ive packaged it for android and started it on the Quest.
After ive got the 2gbi error I had to use the Maps cooking Option in the Package Settings so I had to say wich Maps should be in the Package.
I was still able to Package but I just get Blackscreen on the quest with the three dots. Why would it make this. I dont have the Meta Plugin and old sdk / ndk from a Tutorial but not really integrated. So I dont know why the blackscreen comes now and not from the beginning.
Meanwhile ive added everything like in your Tutorial.
I got the same Blackscreen with three dots like before. i just tryed to get the right Error on Quest.
I hope it was this :
13:55:53.739FamilyIntentScopeAccess denied. Process 10026(com.oculus.presence) cannot receive broadcasts from -1(null)the event is: com.oculus.intent.action.NOTIF_CHANGE
13:55:53.739FamilyIntentScopejava.lang.SecurityException: Access denied. Process 10026(com.oculus.presence) cannot receive broadcasts from -1(null)the event is: com.oculus.intent.action.NOTIF_CHANGE
13:55:53.739FamilyIntentScopeat X.0TQ.A28(:110)
13:55:53.739FamilyIntentScopeat X.0g6.onReceive(:221)
13:55:53.739FamilyIntentScopeat X.0XI.onReceive(:2)
13:55:53.739FamilyIntentScopeat android.app.ActivityThread.handleReceiver(ActivityThread.java:4392)
13:55:53.739FamilyIntentScopeat android.app.ActivityThread.access$1600(ActivityThread.java:258)
13:55:53.739FamilyIntentScopeat android.app.ActivityThread$H.handleMessage(ActivityThread.java:2119)
13:55:53.739FamilyIntentScopeat android.os.Handler.dispatchMessage(Handler.java:106)
13:55:53.739FamilyIntentScopeat android.os.Looper.loopOnce(Looper.java:214)
13:55:53.739FamilyIntentScopeat android.os.Looper.loop(Looper.java:304)
13:55:53.739FamilyIntentScopeat android.app.ActivityThread.main(ActivityThread.java:7918)
13:55:53.739FamilyIntentScopeat java.lang.reflect.Method.invoke(Native Method)
13:55:53.739FamilyIntentScopeat com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
13:55:53.739FamilyIntentScopeat com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1010
Could anyone help me with this ?
