ClassNotFoundException

carmineg · August 2013

I'm not exactly sure where to post this to, but my .APK for OUYA and other Android devices is the same. My game loads fine on OUYA... even loads fine on my Nexus... however I'm getting lots of users with phones reporting errors. I looked at google play store and found several of these errors... I just don't know who/what is causing it. The java part of this thing is sort of like magic to me...

java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.AwesomeApps.Quintet/com.AwesomeApps.Quintet.OuyaUnityApplication}: java.lang.ClassNotFoundException: com.AwesomeApps.Quintet.OuyaUnityApplication

carmineg · August 2013

Maybe this is related to the Android manifest?

tgraupmann · August 2013

Are you using Unity 4.2? Another user had this issue yesterday and upgrading fixed it.

Other things that cause this, is not setting the bundle id. And make sure you hit the sync button and compile the plugin and compile Java.

carmineg · August 2013

I recompiled everything (which is what made me catch that NDK) thing and I re-uploaded it to google play... seeing what happens...

tgraupmann · August 2013

What version of Unity are you using?

carmineg · August 2013

The most recent version (I use a mac by the way). I upgrade whenever it prompts me to. I also have Pro, iOS Pro and Android Pro licenses.

tgraupmann · August 2013

"I have the latest". I've heard that one before; yesterday even. If you do About what version does it say? I think maybe 4.2 failed to prompt users.

carmineg · August 2013

Question... so I'm rebuilding ndk, sdk, java etc.. my build is set for version 14 of the Android SDK... I noticed this happens:

/OuyaUnityApplication.java:26: package android.hardware.input does not exist

import android.hardware.input.InputManager; //API 16

Now the problem is... if I set my minsdk to 16 (instead of 14)... then googleplay excluses 800 devices from the compatible list. This includes the Nexus 7 which runs the game fine (and I use for testing). So having it at minsdk = 14, let's me get more devices... but I'm wondering if the issue is the InputManager is not being found (or not being linked/built/etc.)

My Unity is 4.2.0f

tgraupmann · August 2013

You can use API 14 most likely. But just use the OuyaNativeActivity as your Java Class name which doesn't use the later API.

carmineg · August 2013

I don't under stand what you mean by use the "OuyaNativeActivity" as your java class name...?

tgraupmann · August 2013

Like this and after you change the Java Class Name, you need to sync and recompile the plugin and the Java application:

carmineg · August 2013

- That will make the same .APK work on both OUYA and Android devices?

- Do I need to change the manifest? It specifically says OuyaUnityApplication

tgraupmann · August 2013

The alternative Java file will work on all Android devices, without needing API 16.

The sync button will change the manifest unless you have a bunch in there. If you have multiple activities it will just change the first entry.

You have to manually type in OuyaNativeActivity and hit the sync button.

carmineg · August 2013

So umm... what am I losing by doing this... and why isn't it like this by default then?

(thanks for the help by the way)

tgraupmann · August 2013

It's not the default because it won't work in Unity 3.X. This is a Unity 4.2 or better feature.

You don't lose anything. It's just processing input with Unity's native activity versus passing the input through Java.

carmineg · August 2013

Problems:

Compile Java gives me an error:

javac: file not found: /Data/Development/SpaceGame/Assets/Plugins/Android/src/OuyaNativeActivity.java

Also the OUYA panel is showing me an [error] (bundle mismatched)

The manifest didn't update itself.. so I had to put ".OuyaNativeActivity" in there..

tgraupmann · August 2013

You might have an old update. It should add that automatically now. Hmmmmm I could actually add something to check for updates.... hmmmmm...

carmineg · August 2013

ACK!

I downloaded the latest from Git and now there is now "JoystickType" or "OuyaInputManager" Help!!

(this is getting worse and worse today)

:(

tgraupmann · August 2013

Ah that's legacy stuff I removed. Importing packages doesn't remove files. Just remove the old OuyaInputManager.cs class.

carmineg · August 2013

So...what the heck do I use for joystick now? I don't want to keep using legacy stuff... What replaced

"OuyaInputManager" and "OuyaExampleCommon" for accessing the joystick?

tgraupmann · August 2013

OuyaExampleCommon.cs is still there as the way to get input.

Follow the ShowUnityInput.cs example for input.

In the future I'm starting to add joystick mapping to the OuyaSDK.

That makes the OuyaSDK responsible for getting the mapping for an axisName or a button keycode only. And then you use that and get your input directly from the Unity Input API.

Some new functions coming to the OuyaSDK.

public class OuyaSDK

{

/// <summary>

/// Check if the axis should be inverted after accessing the Unity API

/// </summary>

/// <param name="keyCode"></param>

/// <param name="player"></param>

/// <returns></returns>

public static bool GetAxisInverted(OuyaSDK.KeyEnum keyCode, OuyaSDK.OuyaPlayer player);

/// <summary>

/// Get the AxisName to be used with the Unity API

/// </summary>

/// <param name="keyCode"></param>

/// <param name="player"></param>

/// <returns></returns>

public static string GetUnityAxisName(OuyaSDK.KeyEnum keyCode, OuyaSDK.OuyaPlayer player);

/// <summary>

/// Get the KeyCode to be used with the Unity API

/// </summary>

/// <param name="keyCode"></param>

/// <param name="player"></param>

/// <returns></returns>

public static KeyCode GetUnityKeyCode(OuyaSDK.KeyEnum keyCode, OuyaSDK.OuyaPlayer player);

}

Another cool thing coming is that Joystick mappings are defined in individual files. So check out:

OuyaController.cs

PS2Controller.cs

XBox360Controller.cs

A controller only needs to implement IOuyaController.cs and it becomes a supported controller.

carmineg · August 2013

So... I did the update to make the other thing work... can't compile now... so I sort of need to figure this all out in a crunch because I'm getting 1 star reviews cause my android version won't run on people's things...

Anyway... how do I get joystick type mow? there use to be a nice Joystick class...

tgraupmann · August 2013

Here's how you can check what the controller type is:

IOuyaController controller = OuyaSDK.GetSupportedController(player);

if (controller is OuyaController)

{

//ouya controller
}

else if (controller is PS2Controller)

{

//PS2 controller
}

else if (controller is XBox360Controller)

{

//XBox360Controller controller
}

It's possible you may be using some one else's input, and in that case you can import that solution.

And most importantly for everyone, always use version control.

Ping me on Skype and we'll get you fixed up...

Howdy, Stranger!

Categories

ClassNotFoundException

Comments