Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom web service not syncing SMSes #465

Open
laurentS opened this issue Feb 4, 2017 · 2 comments
Open

custom web service not syncing SMSes #465

laurentS opened this issue Feb 4, 2017 · 2 comments

Comments

@laurentS
Copy link

laurentS commented Feb 4, 2017

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:

{
    "payload": {
        "error": null,
        "success": true
    }
}

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?

@ClearLakeHABMap
Copy link

Seeing this issue too. I am questioning the install directory to the actual route of the endpoint and changes in installations.

@Luk4
Copy link

Luk4 commented Jul 7, 2017

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants