starred/SMSSync

Fork 0

mirror of https://github.com/ushahidi/SMSSync.git synced 2026-04-26 00:05:57 +03:00

[GH-ISSUE #238] Message Results API scheduler is not started after phone shutdown/restart #172

New issue

Closed

opened 2026-02-28 01:23:32 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @sorinpohontu on GitHub (Jan 24, 2015).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/238

Originally assigned to: @eyedol on GitHub.

I'm using "Message Results API", with Frequency check at 1 minute.

After device shutdown or reboot, the Message Results API scheduler is not started.

24-01 16:20 The device has shutdown
24-01 16:21 The device has rebooted
24-01 16:21 Updated scheduler interval
24-01 16:21 Updated scheduler interval
24-01 16:21 Performing task checking
24-01 16:21 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:21 Successfully finished performing task checking null
24-01 16:21 There is active data connection
24-01 16:21 Performing task checking
24-01 16:21 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:21 Successfully finished performing task checking null
24-01 16:22 Performing task checking
24-01 16:22 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:22 Successfully finished performing task checking null

In this case, I have to go to Settings, disable "Message Results API" and re-enabled it.

24-01 16:25 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:25 Successfully finished performing task checking null
24-01 16:25 SMSsync settings - [ Enter alert phone number ] has changed from [  ] to [  ]
24-01 16:26 Performing task checking
24-01 16:26 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:26 Successfully finished performing task checking null
24-01 16:26 Stopping scheduler
24-01 16:26 Scheduler stopped
24-01 16:26 SMSsync settings - [ Enter alert phone number ] has changed from [  ] to [  ]
24-01 16:26 SMSsync settings - [ Enter alert phone number ] has changed from [  ] to [  ]
24-01 16:26 Message Results service started - interval: 60000
24-01 16:26 Updated scheduler interval
24-01 16:27 Performing task checking
24-01 16:27 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}}
24-01 16:27 Successfully finished performing task checking null
24-01 16:27 Checking scheduled message result services

I have tried with both Quick Boot enabled and disabled, it's the same behavior.

Originally created by @sorinpohontu on GitHub (Jan 24, 2015). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/238 Originally assigned to: @eyedol on GitHub. I'm using "Message Results API", with Frequency check at 1 minute. After device shutdown or reboot, the Message Results API scheduler is not started. ``` 24-01 16:20 The device has shutdown 24-01 16:21 The device has rebooted 24-01 16:21 Updated scheduler interval 24-01 16:21 Updated scheduler interval 24-01 16:21 Performing task checking 24-01 16:21 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:21 Successfully finished performing task checking null 24-01 16:21 There is active data connection 24-01 16:21 Performing task checking 24-01 16:21 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:21 Successfully finished performing task checking null 24-01 16:22 Performing task checking 24-01 16:22 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:22 Successfully finished performing task checking null ``` In this case, I have to go to Settings, disable "Message Results API" and re-enabled it. ``` 24-01 16:25 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:25 Successfully finished performing task checking null 24-01 16:25 SMSsync settings - [ Enter alert phone number ] has changed from [ ] to [ ] 24-01 16:26 Performing task checking 24-01 16:26 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:26 Successfully finished performing task checking null 24-01 16:26 Stopping scheduler 24-01 16:26 Scheduler stopped 24-01 16:26 SMSsync settings - [ Enter alert phone number ] has changed from [ ] to [ ] 24-01 16:26 SMSsync settings - [ Enter alert phone number ] has changed from [ ] to [ ] 24-01 16:26 Message Results service started - interval: 60000 24-01 16:26 Updated scheduler interval 24-01 16:27 Performing task checking 24-01 16:27 TaskCheckResponse: SmssyncResponse{payload=Payload{messages=[], task='send', secret='567890', error='null', success=true}} 24-01 16:27 Successfully finished performing task checking null 24-01 16:27 Checking scheduled message result services ``` I have tried with both Quick Boot enabled and disabled, it's the same behavior.

kerem

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

closed this issue
added the
Bug report
label

kerem commented

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

Author

Owner

@eyedol commented on GitHub (Apr 20, 2015):

Could you confirm this is fixed in v2.8.0-rc.1 ?

@eyedol commented on GitHub (Apr 20, 2015): Could you confirm this is fixed in [v2.8.0-rc.1](https://github.com/ushahidi/SMSSync/releases/tag/v2.8.0-rc.1) ?

kerem commented

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

Author

Owner

@sorinpohontu commented on GitHub (Apr 20, 2015):

@eyedol Worked correctly in my latest tests, but I'll have to double check tomorrow and get back to you.

@sorinpohontu commented on GitHub (Apr 20, 2015): @eyedol Worked correctly in my latest tests, but I'll have to double check tomorrow and get back to you.

kerem commented

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

Author

Owner

@sorinpohontu commented on GitHub (Apr 20, 2015):

@eyedol Can you add the apk to 2.8.0-rc-1 release ? :)

@sorinpohontu commented on GitHub (Apr 20, 2015): @eyedol Can you add the apk to 2.8.0-rc-1 release ? :)

kerem commented

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

Author

Owner

@eyedol commented on GitHub (Apr 21, 2015):

@sorinpohontu Added.

@eyedol commented on GitHub (Apr 21, 2015): @sorinpohontu Added.

kerem commented

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

Author

Owner

@sorinpohontu commented on GitHub (Apr 21, 2015):

Seems that services are started after phone reboot on 2.8.0-rc-1. Great :)

@sorinpohontu commented on GitHub (Apr 21, 2015): Seems that services are started after phone reboot on 2.8.0-rc-1. Great :)

kerem referenced this issue

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

[PR #172] [MERGED] Issue #163: Renamed readLogs method to readLog. #390