You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the "test integration" button while adding a custom web service with SMSsync 3.0.5, following the documentation, I'm expecting the test to succeed somehow.
Actual behavior
Instead I keep getting the "Web service doesn't seem to have the right endpoint" error message.
I am also using version 2.7.3 on another set of phones (as it is the only version I've managed to get to work, with the same backend), which works with "success": "true" (note the quotes) in the reply. I have tried that for 3.0.5, but no luck either. Similar tests with quotes around null have not solved it.
The interface seems to have changed between SMSsync 2.7.x and 3.x. What is wrong with my code?
The text was updated successfully, but these errors were encountered:
I don't know if this solves your problem, but I was getting the same error until I changed from https to http. Using http I get "a valid SMSsync service".
Expected behavior
When using the "test integration" button while adding a custom web service with SMSsync 3.0.5, following the documentation, I'm expecting the test to succeed somehow.
Actual behavior
Instead I keep getting the "Web service doesn't seem to have the right endpoint" error message.
Steps to reproduce the behavior
As I am writing the backend, I have followed http://smssync.ushahidi.com/developers/ and return a JSON object like:
I am also using version 2.7.3 on another set of phones (as it is the only version I've managed to get to work, with the same backend), which works with
"success": "true"
(note the quotes) in the reply. I have tried that for 3.0.5, but no luck either. Similar tests with quotes aroundnull
have not solved it.The interface seems to have changed between SMSsync 2.7.x and 3.x. What is wrong with my code?
The text was updated successfully, but these errors were encountered: