I have not had the Fatal Exception issue, but I have had other problems with it, when developing on Ubuntu linux. When I try the example on my Mac, it works. I have been able to narrow it down to the fact that the example attempts to connect to 127.0.1.1:8888 for debugging with a local app engine instance. Upon examining the Util.java file, around the 190 line area, it says to create an assets/ debugging_prefs.properties file with the url of the debug app engine server in it. I tried doing that, but everytime I ran the code, it would revert the url back to 127.0.1.1:8888. The only way that I have been able to get the code to run on linux is to hardcode the url of the dev app engine into the Uitl.java file. This seems to be a bug in the App engine connected project. I have scoured the project settings as well as the other eclipse settings and can not come up with a reason for why it keeps reverting that file.
On May 13, 9:38 am, patjackson52 <[email protected]> wrote: > I've been trying the new app engine connected android projected with > the new beta release and have had no luck. The server side appears to > be working, however the android app crashes. I get a Fatal > Exception: cannot parse payload: payload[0] > > Has anyone else tried this? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
