GoogleVR apk crash on launch

Development Platform & Builds
, , ,
1

Android Cardboard GoogleVR apk build crash on startup.

Step to reproduce:

  1. Start Ue 4.21.1
  2. Create any sample project
  3. Enable GoogleVR plugin
  4. Edit project settings, delete Daydream, leave only Cardboard enabled, enable Googlevr Sustained rate
  5. Choose shipping or development
  6. Package projecy
  7. Transfer project to Android 8 Smartphone (i.e. Moto Z2 Play)
  8. Launch app

Observe: App crashed on launch, touch x to exit.

2

same here, UE4 4.21, Android 8, app crashes on start. Hope someone finds the answer. Subscribed.

3

Yeah,that proplem occurs to me too.So sad…

4

yeah , same problem with me. any solution?

5

so far i could only make it work in 4.19. Not cool to have to downgrade though.

6

yes totally not cool, i download the 4.20.3 version and it is working well, tnx

7

I am having this issue as well and I can’t seem to open the file in 4.20.3. Any help to help open in the older version would be greatly appreciated. It says '(file map) is a UE4 map [File:v517], from an engine release newer than this [Cur:v516]

8

Hi All,

I also got this issue and as it seems, versions 20, 21 and 22 got the problem for android compilation. Version 19 works fine.
Looking more into the error it seems to be related to the “splash screen” for the google cardboard. The ones that asks you to insert your phone on the device. Searching on the logs, the error is related to some typo error on the java classes that works beneath the unreal engine code for android. For some reason it got messed up on the newer versions.

I was not able to solve that, but if someone knows how, there are some stuff we can try.

  1. Remove the splash screen entirel. (not sure how)

  2. Create the package only for google cardboard, remove any reference for steamVR and daydream. (did not try)

  3. Export your project files as FBX and inport on a 4.19 engine. Then, remake the blueprints, materials, and settings. (This one works)

Regards,

9

well 4.20.3 is fine, at least for me. The problem has been introduced in 4.21.