Blocked User: Location should be removed from widget without kill/reload required

[mstidham]

Blocked User: Location should be removed from widget without kill/reload required

QA TEMPLATE	Input
Device Type:	iPhone 7 Plus
iOS:	11.4.1
tr Version:	3.4.2
Environment	Staging
Codepush:
Internet Connection Type:	WiFi
Users affected?	Miranda
User handle:	@miranda
Bypass handle?:	@bic (123-1114)
Location access type?	Always
Does this issue occur on other environments?
Time issue occurred (UTC)

Observed Result:

@miranda blocked @bic (bypass account) without killing the app the user @bic still had @miranda’s location “The Stidham Residence” on the widget. @bic tapped and does see the Oops screen but all images below are visible. Location is removed from the widget with a kill/reload.

Expected Result:

Location should be removed from the widget when a user is blocked. Kill/reload should not be required to remove location from widget.

Steps to reproduce:

1. Block user that is in a location (location visible on widget)
2. Location remains on the widget and is tappable.
3. Images on Location Profile are still visible.

Related Screenshots/Video Links:

---

[bengtan]

There's two symptoms here.

1. the user @bic still had @miranda’s location “The Stidham Residence” on the widget.

2. @bic tapped and does see the Oops screen but all images below are visible.

I'll come back to 1 later.

Symptom 2 is definitely a bug. Should be reasonably reasonable to hide all the images and stuff (even if already cached on the client) if the parent Bot/Location isn't loadable/viewable.

As for 1 ... I'm not sure if it's important enough to squeeze into the App Store release.

Maybe we can spin out 1 and 2, and leave 1 for another time? Probably needs more discussion.

[aksonov]

I've fixed #2 as part of #2825.

[bengtan]

@scurry:

Can we punt 1 until later?

To fix it, we'd need to implement 'live updates' for blocked users (on server and client side), and I don't think it's important enough to delay the release for.

[aksonov]

Bump

[southerneer]

Ha! @bengtan [at]scurry is not on our team ;) Maybe @thescurry can help

[thescurry]

Yes, sorry I missed this ticket earlier. We can punt on 1 and pick it up on the polish after app store submission.

[bengtan]

So we should only QA the second part:

@bic tapped and does see the Oops screen but all images below are visible.

[mstidham]

Verified on Staging Version: 3.8.1

[mstidham]

Verified on Prod Version: 3.8.1