mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 15:55:57 +03:00
[GH-ISSUE #199] Only first set of sync rules work #142
Labels
No labels
Bug report
Code improvement
Concern
Feature request
Feature request
Good first issue to work on
In progress
Needs info
Question
Ready
Translation
User Experience
User Experience
Website
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SMSSync#142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @redbullpeter on GitHub (Sep 22, 2014).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/199
When I defined two or more sets of Sync URL rules, only the first active rule works. See the following scenarios that work and don't work:
Sync rule 1 (Active) - works
Sync rule 2 (Active) - does not work
Sync rule 1 (Inactive) - inactive
Sync rule 2 (Active) - works
Sync rule 1 (Active) - works
Sync rule 2 (Inactive) - inactive
Sync rule 1 (Active) - works
Sync rule 2 (Active) - does not work
Sync rule 3 (Active) - does not work
Sync rule 1 (Inactive) - inactive
Sync rule 2 (Active) - works
Sync rule 3 (Active) - does not work
Sync rule 1 (Active) - works
Sync rule 2 (Inactive) - inactive
Sync rule 3 (Active) - does not work
Sync rule 1 (Inactive) - inactive
Sync rule 2 (Inactive) - inactive
Sync rule 3 (Active) - works
The behaviour observed is that, the first active rule works as expected. The subsequent rules do not work and the message is in pending state. As soon as the first active rule is deactivated, the next rule (which is now first) instantly works and the subsequent rules don't work.
Version I am using is 2.6.1
The problem appears to be independent of the make, model and android version.
@cavpollo commented on GitHub (Oct 29, 2014):
Same here.
Using the version 2.6.1 on a Galaxy S3 with android 4.3.1 the exact same result mentioned above occurs.
@sorinpohontu commented on GitHub (Apr 21, 2015):
@eyedol I think you can close this issue for 2.8.0.