Forum | Appery.io

Hi Jeff,
Sorry for the delay.

Line breaks in test output is not affect to response in app. Currently, for me your service is not responding at all.

For current state of project:
ulliI find you don't use proxy on RESTService. Its important for tests in browser (for json-requests) but no need on device or for jsonp-requests. /li
liYour Generic service have syntax mistake. prefunction httpGet(http://www.)/pre this line and a whole generic service can't works as you expected. Please, check this document for details./li
/ul

Anton,

I've tested it with and without proxy. I've tested with json, jsonp, xml, every combination therein. None of these settings work. So by the time you got around to looking at the project, there's no telling what the settings were at that point in time. I've been doing constant testing of various settings to see what will work, and so far nothing will...and it is ALL based on that issue of the line break in the Response window, it seems.

I can take the URL you listed (the one used by the service) and put it in http://hurl.it and copy the response that I get into the JSONLint validator and it is 'Valid JSON.' If I copy the response from appery.io, I see that it is adding line breaks to the text in the "Response" section of the service.

Hello!

You will need to delete JS asset 'JavaScript1' and service 'GenericService' as well.
Also check mapping: delete arrow to html_10 as response parameter of page is not an array.

I could kiss you, Alena! The javascript and GenericService didn't really appear to be an issue; however, the mapping of 'page' as an array was the real issue. Thank you so much!

Also, in Anton's post above where he references a URL in his httpGet example, could I have that removed, please? Thanks in advance.

I can remove the entire post.. or have Anton edit it?

Either is fine. For other users to potentially benefit from this post, it might be a good idea to keep it up for future reference. So I'd say just edit the URL.

I'm sorry... Post edited.

But from my perspective, all sensitive API always must have some security keys or authentication headers. Security based on secret URL is always not so secure as it looks.