Getting the same error here in emulator. Either when starting the launcher or trying to show the details to an app (where I could understand it, since its pushed into the emulator and not on the server), but I guess launcher should somehow work?
The device id (as shown in menu and in the request URL in the log) is -787269460.
I also reseted the launcher, but had to skip the pairing (having no bluetooth available in the emulator) and had to skip the video, because it lags unviewable. I skipped both steps by pressing the home button, which eventually took me to the main menu screen.
Just some other information on the device serial. The emulator Build.SERIAL (that you check in your Serial tv.ouya.console.util.SerialNumber class is "unknown", so your generation code is used to generate the serial number. Since you use the hash code of the Long class, what result in an (unsigned) integer, that value is a total valid outcome of the generation method (but as it seem, not the best to communicate with your server :) ).
In general I would like to add: I think the ODK is very good in several ways. You don't mess up with users' privacy (by generating unique user ids, for every app), you offer JAR libraries, what is way easier, as if you would have forced to use some custom project structure, and much more, what I really like so far. Thanks for all that already, and thanks in advance for the fix of this bug :)
Justin: The server just denies the generated serial numbers. There is only one possible fix for the client side. Find someone with a hardware device, willing to give you their serial number, so you could save it in the emulator. I guess these won't get denied, since I haven't heard anyone with a hardware device complaining about that error.
@TomTom: Ah that makes sense. Well no sense in worrying about it to much then. I'm sure we'll see more ODK updates as we get closer to launch and this will probably get fixed sooner or later.
pixjuegos
Posts: 73Member
Comments
Android Specialist
OUYA
Full paste can be found under pastebin.com/6ec2M12R
The device id (as shown in menu and in the request URL in the log) is -787269460.
I also reseted the launcher, but had to skip the pairing (having no bluetooth available in the emulator) and had to skip the video, because it lags unviewable. I skipped both steps by pressing the home button, which eventually took me to the main menu screen.
WiFi MAC Adress:
Ethernet MAC Address: 52:54:00:12:34:56
Bluetooth MAC Address:
Build Number:
Hardware Version: OUYA
Software Version: 0.04
In general I would like to add: I think the ODK is very good in several ways. You don't mess up with users' privacy (by generating unique user ids, for every app), you offer JAR libraries, what is way easier, as if you would have forced to use some custom project structure, and much more, what I really like so far. Thanks for all that already, and thanks in advance for the fix of this bug :)