[GH-ISSUE #129] No Secret value, No Task Checking #101

New issue

Closed

opened 2026-02-28 01:23:11 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 01:23:11 +03:00

Owner

Originally created by @eyedol on GitHub (Oct 9, 2013).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/129

This has bee reported on the forums. Logging it here so it can be fixed.

We have confirmed the presence of this bug in v2.4:

When Secret Key is not set and Task Checking is enabled we see the following GET:
"GET /smssync HTTP/1.1" 200 32 "" "SMSSync-Android/v2.4"
When Secret Key is set and Task Checking is enabled, instead we see:
"GET /smssync?task=send&secret=10001 HTTP/1.1" 200 32 "" "SMSSync-Android/v2.4"
(It seems to be worse in v2.5-DEBUG with no parameters being passed even when Secret Key is set.)
Finally, every time SMSSync accesses our server, it would be extremely useful to have uniqueid=unique_id included in the parameters.

You can follow the thread.

Originally created by @eyedol on GitHub (Oct 9, 2013). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/129 This has bee reported on the forums. Logging it here so it can be fixed. We have confirmed the presence of this bug in v2.4: 1) When Secret Key is not set and Task Checking is enabled we see the following GET: "GET /smssync HTTP/1.1" 200 32 "" "SMSSync-Android/v2.4" 2) When Secret Key is set and Task Checking is enabled, instead we see: "GET /smssync?task=send&secret=10001 HTTP/1.1" 200 32 "" "SMSSync-Android/v2.4" (It seems to be worse in v2.5-DEBUG with no parameters being passed even when Secret Key is set.) Finally, every time SMSSync accesses our server, it would be extremely useful to have uniqueid=unique_id included in the parameters. You can follow the [thread](https://wiki.ushahidi.com/display/forums/Anyone+get+tasks+working+with+SMSSync).