Closed GoogleCodeExporter closed 9 years ago
Original comment by mitchellsundt@gmail.com
on 9 Jul 2011 at 3:52
There's not enough information here to act. Please attach a copy of the form.
Original comment by carlhart...@gmail.com
on 27 Sep 2011 at 8:11
The problem is that at
http://code.google.com/p/opendatakit/source/browse/src/org/odk/collect/android/t
asks/InstanceUploaderTask.java?repo=collect#201
The entity is null. This is likely a network login screen or PHP server or
something returning other than 204 on a HEAD request. This isn't form-specific.
Original comment by mitchellsundt@gmail.com
on 27 Sep 2011 at 8:28
If helpful, I am experiencing a similar issue with Aggregate 0.9.7 and an xform
from Collect 1.1.7. Xform attached. Strangely the fusiontable gets created.
The issue repeats for all publish to fusiontable attempts. i.e.
* Press connect fusion table
* Stream new data
* Grant (allow) anonymous
Error message shown on screen to me is:
Uncaught exception from servlet
java.io.IOException: com.google.gdata.util.ServiceException:
<HTML><HEAD><TITLE>Unauthorized</TITLE></HEAD><BODY BGCOLOR="#FFFFFF"
TEXT="#000000"><H1>Unauthorized</H1><H2>Error 401</H2></BODY></HTML>CREATE
TABLE 'xacprod03'
('SubmissionDate':datetime,'sysnum':string,'dev_prsnt':string,'dev_type':string,
'lat_long':location,'lat_longAltitude':location,'lat_longAccuracy':location,'ins
talled':string)
at org.odk.aggregate.servlet.FusionTableServlet.doGet(FusionTableServlet.java:155)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
Original comment by jamespda...@gmail.com
on 29 Sep 2011 at 1:21
Attachments:
James, the issue you're describing is an issue with Aggregate. This bug is
about a crash in Collect. Please open another bug in the issue tracker.
Original comment by carlhart...@gmail.com
on 4 Oct 2011 at 5:58
I can't reproduce this bug. Network login screens pop a dialog indicating a
bad response and suggesting they need to log in (I just updated the error
message to be a little more clear), or the dialog says timeout.
Original comment by carlhart...@gmail.com
on 4 Oct 2011 at 6:00
Original issue reported on code.google.com by
mitchellsundt@gmail.com
on 24 Jun 2011 at 6:08Attachments: