Forum | Appery.io

Hi Igor,

Thanks for the response. I am not using the Zoho Creator API in this scenario for a very specific reason, which I don't need to bore you with.

The fact is that I can use the URL and Post params from CURL without any issues. It gives the correct response back. Also, the service does send the data from here to Zoho, it's just displaying the error msg as the result mentioned above.

So, let's pretend that this is NOT Zoho that I'm connecting to for the web service, and just try to work on the issue from that perspective.

Thanks!

Hello! Perhaps you have incorrect settings. Could you show us curl command? You can sent it to a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a

I think you may be right... I've sent the curl command to support.

This will take some time. We'll update.

Hello! Still no news... We're working on it.

Ok. Thank you for the update.

Hello,

Yes, in our testings we are getting this error:
pre
Failure parsing MediaType string: text
/pre

Please check this in your service - why it's occurs.

Yes, that is the same message is that is part of the error message that I've originally posted. If I knew why it was happening, I wouldn't have posted this question. I'm confused as to why you would be asking me to "check this in your service" ?? Like I mentioned before, the web service is OK, I can use curl to post and receive the proper response.

Thanks!

Hello! Sorry for a late reply. Here is the problem...
When you call your service from Appery.io back-end (service Test tab or call through Appery.io proxy) it gives server error for some reason (looks like a bug, we'll research it more). As a workaround run browser in "Disable same origin policy" mode. This way you'll be able to work with services in browser (remember that for services you have problem with you would need to disable Appery.io proxy in service settings). Unfortunately there is no workaround for Test tab. If you install apk/ipa on device and test with disabled proxy it will work.

Thank you!

Of course it would be a newbie that manages to find a bug... I spent quite a bit of time trying to make that service work..

I will try your workaround suggestion for the browser.

Thanks again, and please keep me posted when this is resolved.