Big Daddy example problems
65 views
Skip to first unread message
patjackson52
May 13, 2011, 10:38:55 AM5/13/11
to Google Web Toolkit
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?
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?
bbgott
May 25, 2011, 2:36:58 PM5/25/11
to Google Web Toolkit
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.
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.
Zachariah Young
May 30, 2011, 5:37:10 PM5/30/11
to google-we...@googlegroups.com
@bbgott
I'm getting the same issue also on Ubuntu. The solutions work just fine on Windows. Could it be that Ubuntu has the 8888 port blocked or something?
Also what did u hard code to get the Android application to work.
Adolfo Panizo Touzon
May 31, 2011, 6:07:39 AM5/31/11
to google-we...@googlegroups.com
Can the application runs in other port??
--
El precio es lo que pagas. El valor es lo que recibes.
Warren Buffet
2011/5/30 Zachariah Young <zpy...@gmail.com>
@bbgottI'm getting the same issue also on Ubuntu. The solutions work just fine on Windows. Could it be that Ubuntu has the 8888 port blocked or something?Also what did u hard code to get the Android application to work.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
El precio es lo que pagas. El valor es lo que recibes.
Warren Buffet
Ed
May 31, 2011, 9:37:44 AM5/31/11
to google-we...@googlegroups.com
Try running netstat as root on the linux machine to determine if the
port is in use
port is in use
bbgott
Jun 16, 2011, 5:35:15 PM6/16/11
to Google Web Toolkit
I found that if I put the external ip of the development machine into
the debugging_prefs.properties file and then set the file read-only,
the project would work. The downside to this approach is that it
requires me to change the file with each environment that I program
in. For some reason, eclipse overwrites the file on compile if it is
not read-only. The contents of my file is "url=<external ip>:8888"
and the file privileges are set to -r--r-----.
the debugging_prefs.properties file and then set the file read-only,
the project would work. The downside to this approach is that it
requires me to change the file with each environment that I program
in. For some reason, eclipse overwrites the file on compile if it is
not read-only. The contents of my file is "url=<external ip>:8888"
and the file privileges are set to -r--r-----.
Reply all
Reply to author
Forward
0 new messages