Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I am unable to verify your issue as described (using your provided src, it works in my dev environment using a JB emulator), though I have seen your specified error during development of the Android library. I have found that many of the "Serialization" issues in GWT are usually something small such as unserializable member types, missing interfaces, default constructors, etc. Since it seems you have already addressed those possibilities, please verify the following: </p> <p>Version of GWT being used in web-app on your machine. Android OS Version being tested on (emulator or Device) and which device if appropriate.</p> <p>Though I dont expect it to be an issue, the Android library is compiled with GWT 2.5.0 src, so it's possible (an as yet untested theory) that if the server is running GWT other than 2.5.0, the RPC serialization is failing due to that. </p> <p>This would also explain why the desktop client works and the android library does not. The desktop client syncproxy library is compiled against GWT, not with GWT, so you link your version of GWT at compile time. The Android library was compiled directly with GWT src code for 2.5.0 with a few custom overrides in order to reduce the size of the library to be usable and manageable in the Dalvik environment.</p> <p><strong>That said, if its possible for your project, try using GWT 2.5.0, clean/recompile and give that a shot. If not, it's on my todo list to get the library up to 2.5.1, but I haven't had time as yet.</strong></p> <p><em>Disclaimer: I created the Android library in question as a contributor to the gwt-syncproxy project. I can't claim to understand all the ins and outs of GWT or the syncproxy internals, but at least enough to get the working model of the library functional. I'm open to suggestions on improvement of the library or any ideas of where in the internals we should look to resolve this if any gwt-guru's are out there...</em></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload