mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 15:55:57 +03:00
[GH-ISSUE #233] Crash on sending a SMS which fails #171
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#171
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 @sorinpohontu on GitHub (Jan 21, 2015).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/233
Originally assigned to: @eyedol on GitHub.
Hello.
I'm in the final steps of integration with SMSSync and I've made a test with a SMS which will fail (in my case, Insufficient credit available).
In this case, SMSSync is crashing, after trying to re-send the message 10 or 11 times.
Android version: 4.2.2
SMSSync: 2.7.3
Here is the SMSync Log:
The message is still in SMSSync queue and will be retried a few times (note: it should be possible to set the number of retries), until the app crash.
There is no error in SMSSync log.
But, there are some errors and exceptions in system logs:
followed by
You'll find the complete log here: https://gist.github.com/sorinpohontu/5c571dcd1beb69c6511f
Let me know if you need more info.
Have a nice day,
/Sorin
@sorinpohontu commented on GitHub (Jan 21, 2015):
Hello. I've tried debug the application and to see on log exactly when "Unfortunately, SMSsync has stopped" and it seems to be here:
Hope that would help :)
@sorinpohontu commented on GitHub (Jan 21, 2015):
And an additional note: The app still crashed if "Enable Message Results API" is disabled, with same error in syslog as above (Producer method for type boolean found ...).
Initially, I had the impression that it related to Message Results API response.
@eyedol commented on GitHub (Jan 21, 2015):
@sorinpohontu These are helpful. We will push a fix soon. Thanks
@eyedol commented on GitHub (Jan 24, 2015):
@sorinpohontu want to test the fix? I can't really produce it on my device. You can catch me on IRC freenode.net, #ushahidi
@eyedol commented on GitHub (Apr 20, 2015):
@sorinpohontu could you confirm this is fixed in v2.8.0-rc.1
@sorinpohontu commented on GitHub (Apr 20, 2015):
@eyedol Seems to be fixed :)