Skip to main content
motorsep
Inspiring
February 15, 2019

[GO] UE 4.21.2 + 1.34 app instantly closes after launch

I moved from UE 4.21.1 + 1.32 to UE 4.21.2 + 1.34. Everything works fine when using UE 4.21.1.

First there were issues with Audio SDK which prevented UE4 from even packaging the project. Oculus fixed that in timely fashion, which I am grateful for.

Now it's this:

02-14 18:14:00.750  3546  3563 D UE4     : Fatal error: [File:E:\UE4Source\UE-oculus-4212-release-1340\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformProcess.cpp] [Line: 45] 
02-14 18:14:00.750  3546  3563 D UE4     : FPlatformProcess::GetDllExport not implemented on this platform
02-14 18:14:00.750  3546  3563 D UE4     : Assertion failed:  [File:E:\UE4Source\UE-oculus-4212-release-1340\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformProcess.cpp] [Line: 45] 
02-14 18:14:00.750  3546  3563 D UE4     : FPlatformProcess::GetDllExport not implemented on this platform
02-14 18:14:00.750  3546  3563 D UE4     : LogAndroid: Error: === Critical error: ===

Basically as soon as I launch my app on Go, it goes into black screen and instantly shuts down.

Has anyone experienced such issue ? 


    This topic has been closed for replies.

    16 replies

    Show previous replies
    motorsepAuthor
    Inspiring
    February 18, 2019

    prokshit said:

    Check in Project Settings 
    - Go to bottom end  - OculusVR and Launch Utilities - Select Mobile and Click on all the suggestions like android config..etc
    - Make sure your android sdk is Android 21, higher version not supported. 
    - Uncheck the "Use Gradle instead of Ant", Gradle builds on the higher android version.
    - Textures format is ASTC, I think you already know this.
    Try these and let me know.


    This isn't my first rodeo.. Android 23 works fine (and required for Quest). I've been using Gradle since it was implemented into UE4 - never had any issues. I used to pack with ETC2, now I am using ASTC, but it has _nothing_ to do with the fatal error I am getting.

    The only thing that might help is "Launch Utilities" - I don't recall seeing it in 4.21.1 + 1.32 Oculus fork.

    The issue with this fatal error is Audio SDK. I wasn't even packaging for Go initially. Oculus fixed that. Now it doesn't eve run (because it packages for Windows apparently, even if I am packaging for Android).
    motorsepAuthor
    Inspiring
    February 18, 2019
    I am not a C++ programmer, but it looks like Android isn't even supported (I might be wrong though):

    https://github.com/Oculus-VR/UnrealEngine/blob/91f23fa7c51595d7af18cf94f0ab3cc73df0ec60/Engine/Plugins/Runtime/Oculus/OculusAudio/Source/OculusAudio/Private/OculusAudioDllManager.cpp

    In FOculusAudioLibraryManager::LoadDll() you see // PAS TODO: support middleware on android. There is only #if to handle Windows platform.
    motorsepAuthor
    Inspiring
    February 19, 2019

    prokshit said:

    Check in Project Settings 
    - Go to bottom end  - OculusVR and Launch Utilities - Select Mobile and Click on all the suggestions like android config..etc



    No-go either.
    prokshit
    Participant
    February 19, 2019
    Glad to hear this isn't your first rodeo, I had mine couple days ago and it sucked. Anyways I faced the same issue and I fixed it but I just can't seem to remember what it was exactly that fixed it. Don't know if it was audio or not but as soon as I opened my App on GO, black screen and then back to the oculus main menu screen.
    This is what I did as much as I can remember - 
    - Using Ant and Instead of Gradle which I still suggest you give that a shot. 
    - I downloaded and updated all the android extra stuff inside the SDK manager.
    burtonposey
    New Participant
    March 14, 2019
    Having the same issue myself. Whether or not I'm specifying to use the Oculus Audio plugin, I am still getting an immediate crash back to the menu when I launch. However, when I disable the Oculus Audio plugin from the project altogether, the application loads without issue.
    mfmf
    Inspiring
    April 3, 2019
    Hey folks-- sorry for the delay. We've patched this issue in the 4.21 version available in our github.
    Terms & ConditionsAccessibility statement