if you PRINT *something*, you don't return *something* to the device, but you can see the *something* on the console, .i.e. the shell where you started web2py.py . I'm guessing that at least you have access to your developing environment :P !
On Tuesday, October 23, 2012 3:38:26 PM UTC+2, Mchurch wrote: > > but i don't open that page in a browser, i'm just sending data. > Should I use a console error like firebug may be? > Sorry for the stupid question, but if i open the page in a browser without > the data from ios i get from web2py "Expected string o JSON...". > I'm lost somewhere between IOs and web2py!!! Be patient Niphlod... > :) > > Il giorno martedì 23 ottobre 2012 15:30:42 UTC+2, Niphlod ha scritto: >> >> What I said was that if you print on the server-side you can see what >> happens on the "endpoint" you have control of: not IOS, the webserver! >> >> On Tuesday, October 23, 2012 3:27:46 PM UTC+2, Mchurch wrote: >>> >>> from the app, no more errors, always that "500". >>> >>>> try to print out request.vars and request.vars.body.read() and see >>>> their contents. >>>> >>> >>> I have to think and study more about that; it's a json call, i can't >>> reach directly that page, i should give the server response back to the app >>> to check what web2py reads. >>> But from IOS i don't know (yet) how to do! >>> Thanks Niphlod. >>> >>> Il giorno martedì 23 ottobre 2012 11:55:16 UTC+2, Niphlod ha scritto: >>>> >>>> that's the problem when you don't know what something does..... >>>> >>>> try to print out request.vars and request.vars.body.read() and see >>>>> their contents. >>>> >>>> >>>> PS: you can also watch the errors for the app to investigate the issue >>>> (if your phone is getting a 500, it's probable that the error is logged in >>>> web2py) >>>> >>>> --
