Unity editor crashes

[Jocarfl]

When I hit play from the Unity editor it crashes directly. In the log I get these errors:

From what I've been seeing it has to do with the sdk/jdk. In the Player Editor I have API Level 27 (Android 8.1) as indicated in the project. Do I have to install any specific SDK?

Thanks

[GRamosPlux]

Dear @Jocarfl,

Thank you very much for sharing this event with the team, we sincerely wish that everything is well with you.

The situation is really curious, indeed.
In order to evaluate its potential source, hoping that you don't consider inadequate, the team would like to check if 1) the error is raised while running our unity-android-sample project unmodified; 2) if the error also occurs when the File >>> Build And Run option is clicked instead of the Play button and 3) which is the model of the Android Tablet/Smartphone being used and its Android Version?

I will carefully wait for your valuable feedback, wishing, in the meantime, a continuation of an excellent day!

My best and sincere regards,
@GRamosPlux

[Jocarfl]

Hello, thank you for replying!

Yes, I'm running the project without modifications, the only things I've configured are the ones indicated in the readme, so far I've only tested it by hitting play from the editor. I want to implement the functionalities in a project I have for Meta Quest 3 that will collect the data from the sensors. I am working with this version:

And the JDK/SDK I'm using are the default ones you download when installing version 2022.1.16. Even though it says ‘You are missing the recommended JDK...’. I have installed all the modules it asked for, I don't know why this error appears.

I am logged in to Unity services and I have their licenses up to date, it is the only project where I get this error:

I look forward to your comments, thanks for replying and have a nice day! :)

[GRamosPlux]

Dear @Jocarfl,

The team is grateful for your kind update and valuable clarifications.

Taking into consideration the detailed information that you gently provided, we were able to replicate the error.
Apparently, the OpenJDK version installed by Unity Hub is based on Java 11 and our project requires Java 8.

In order to overtake this obstacle, the Java 8 SDK | Windows 64 bits (download link) should be manually installed.

After the installation, the following path should be replaced by C:\Program Files\Java\jdk1.8.0_202

Then, the Unity and Unity Hub should be closed and relaunched.

Once relaunched, it is recommended to Reimport All Assets 😉

We will carefully wait for your valuable feedback regarding the effectiveness of the previous suggestions, wishing, in the meantime, a continuation of an excellent day!

My best and sincere regards,
@GRamosPlux

[Jocarfl]

Hi @GRamosPlux , thanks for the answer!

We have tried what you have told us and Unity has crashed again, and the logs are the same as the first time #7 (comment). We have tried to put a try/catch in the script DeviceController:

try
{
    // Establishing the context of the Android activity.
    activityContext = activityClass.GetStatic<AndroidJavaObject>("currentActivity");
}
catch (Exception e)
{
    Debug.Log("currentActivity not found");
}

and MainScreenManager:

private int getSDKInt()
{
    try
    {
        using (var version = new AndroidJavaClass("android.os.Build$VERSION"))
        {
            return version.GetStatic<int>("SDK_INT");
        }
    }
    catch (Exception e)
    {
        Debug.Log("SDK not found");
        return -1;
    }
}

With these changes, the editor doesn't crash and it works when you press play, although for the moment we haven't been able to test if everything works correctly (that it finds the sensors and can read data). I'll let you know when we know if it works correctly.

UPDATE: When building and running the apk on a device, it works correctly scanning and finding devices. But in the unit editor it does not find any devices.

[GRamosPlux]

Dear @Jocarfl,

The team strongly hopes that the last few days have been really positive for you, and I would like to apologize for my late reply.

We are really glad for understanding that you were able to identify a workaround, these are excellent news 🎉

Regarding your kind UPDATE, despite being less practical for the developer, considering that it will take more time, this is the expected behaviour considering the architecture behind our API.

I will keep the current issue open until the team makes a new release/fix.
Please, if any new issue appears, do not hesitate to comment here or create a new issue 😉

In the meantime, the team wishes you a continuation of an excellent week, full of exciting moments in your development.

My best and sincere regards,
@GRamosPlux