mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 15:55:57 +03:00
[GH-ISSUE #12] 2 SMS's within a few seconds of each other: 1 not picked up into app #9
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#9
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 @alilienthal on GitHub (Feb 10, 2012).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/12
Hello,
I received 2 SMS's within a few seconds of each other from the same sender. The second one was picked up by the app, but the first one was not. Closing/restarting the app, synchronizing, etc. did not force the app to pick up this missing message. Is there some concurrency problem where if the app is doing something when a new SMS comes in, it won't pick up the SMS?
@alilienthal commented on GitHub (Feb 10, 2012):
It looks like it happens when there is a pending SMS that is "stuck" for a while. For some reason, a message will not send, even when there are no network problems and the server is responding correctly. During this time period, other messages will not be picked up by the app at all. It's like this pending SMS is "blocking" all new received SMS's from entering the app.
@eyedol commented on GitHub (Aug 17, 2012):
@alilienthal Was the server returning the correct status response to the gateway?