search

CityOfBoston / CityWorker-issues-Incapsulate

Archived for legacy purposes
0 stars 0 forks source link

Cityworker not refreshing when creating new case #112

Closed Gerardovillanueva closed 6 years ago

Gerardovillanueva commented 6 years ago

When you create a new case on cityworker the status of the case stays "submitted" however the case is created. You have to manually refresh cityworker for status to change.

https://drive.google.com/open?id=0B3l27HBycWVpeUtQa1hxZXlIcWViWjJzcVE5eU1qZDA4UlRZ

limadog2003 commented 6 years ago

This wasn't the case yesterday, so it seems something has changed from then to today on this. There doesn't seem to be any automatic synching happening right now on any element.

jqr commented 6 years ago

@Gerardovillanueva We've not been able to reproduce this, can you tell us any more about what you were doing when this was happening?

limadog2003 commented 6 years ago

I was able to reproduce with an Android. The system when submitting a new case/closing a case/reallocating, etc. will communicate and perform the requested action via salesforce (we can see it update within the system), but the final step of updating the case on CW to closed/open/reallocate doesn't seem to be completing without hitting the manual synch button. Otherwise it will stay in a "submitted" status on the screen. @jqr

Gerardovillanueva commented 6 years ago

@jqr I have tested this on Android and its not just me, I have ask my co-worker to tested @limadog2003 and he is having the same issue.

jqr commented 6 years ago

@Gerardovillanueva I believe you, just trying to recreate on my side! Could you answer the questions above to give me a hand?

Gerardovillanueva commented 6 years ago

@jqr The automatic syncing seems to be working now!

jqr commented 6 years ago

@Gerardovillanueva Happy to hear it, but if you could answer the above questions that would be a big help for us!

Gerardovillanueva commented 6 years ago

OS: Android Were you doing anything odd when this happened? Just doing normal cityworker cases Can you reproduce this? The issue was ongoing for every case Does force quitting the application fix it? Yes, When you force quit the application cityworker automatically syncs How would you characterize your use: I do keep the app open for a long time and I use a different phone to test BOS311 app; I rarely force quit the app.

jqr commented 6 years ago

@Gerardovillanueva I think this issue was intermittent and really hard to recreate, but we've made some improvements in Build 512 that should help dramatically. Here's some background if you're curious.

On iOS, the push notification system disconnects as soon as the device goes into sleep, or shortly after switching applications. On Android it stays connected for minutes, likely hours. This is a difference in how Android and iOS applications are allowed to run in the background.

Normally this difference is fine but occasionally the Android device can become disconnected and not realize it. Which causes it to think that it's seeing a list of all changes as they happen, so no need to do any ad-hoc refreshing. In reality it is disconnected and will never see another update notification.

We've fixed this by disconnecting the Android client much more frequently, causing it to revert to behavior similar to iOS.

So, we think this is fixed, but please re-open if you're seeing this on version Build 512 or later.

jqr commented 6 years ago

Sorry, make that Build 517 🙂

Gerardovillanueva commented 6 years ago

Hi Elijah,

Got it, Thank you for the update.

On Mon, May 21, 2018 at 9:01 AM, Elijah Miller notifications@github.com wrote:

Sorry, make that Build 517 🙂

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/CityOfBoston/CityWorker-issues/issues/112#issuecomment-390647097, or mute the thread https://github.com/notifications/unsubscribe-auth/AkH0ORynvZ2Qy1lgLEIBUlb2GuM8EBsgks5t0rqPgaJpZM4TuE7R .