[GH-ISSUE #465] custom web service not syncing SMSes #329

New issue

Open

opened 2026-02-28 01:24:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 01:24:10 +03:00

Owner

Originally created by @laurentS on GitHub (Feb 4, 2017).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/465

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?

Originally created by @laurentS on GitHub (Feb 4, 2017). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/465 ### 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?

kerem commented

2026-02-28 01:24:10 +03:00

Author

Owner

@ClearLakeHABMap commented on GitHub (May 22, 2017):

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

@ClearLakeHABMap commented on GitHub (May 22, 2017): Seeing this issue too. I am questioning the install directory to the actual route of the endpoint and changes in installations.

kerem commented

2026-02-28 01:24:10 +03:00

Author

Owner

@Luk4 commented on GitHub (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".

@Luk4 commented on GitHub (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".