search

hippware / rn-chat

MIT License
5 stars 0 forks source link

Notifications: Infinite loader on Requests tab #4191

Closed mstidham closed 4 years ago

mstidham commented 5 years ago

User occasionally has an infinite loader on the Request tab. Issue is usually corrected with a kill/reload.

Snip20190926_7

bengtan commented 5 years ago

Is this a recent thing? ie. only on 4.26.0? Or it's been happening before 4.26.0?

mstidham commented 5 years ago

@bengtan I was experiencing a blank Request tab but haven't seen the infinite loader.

mstidham commented 5 years ago

I experienced this again today and all I did was run into town. I had invisible mode on and removed it once I was at my location. I then navigated to the Requests tab and had the infinite loader. I have tried reproducing this issue and have been unsuccessful.

image

bengtan commented 5 years ago

Note to self: Investigated but didn't find anything.

mstidham commented 4 years ago

I'm still seeing this issue on android & ios, Staging & Prod Version: 4.29.1

User A has the app open and receives an invite (location, friend etc.). User A navigates to the notification screen and will see the new invite but the infinite loader is below and nothing else ever loads.

image

mstidham commented 4 years ago

I'm still seeing this occasionally on Version: 4.30.1

mstidham commented 4 years ago

Prod Version: 4.32.1 (4.32.0-v-23) I'm still seeing this and have figured out steps to reproduce. If user backs out of the Updates and returns everything loads correctly. I also experienced an app crash when tapping on the Requests tab previously and noted it on #4326.
Steps:

  1. Open the app and immediately tap on the menu button
  2. Tap Updates
  3. Tap Requests tab
  4. I consistently see the infinite loader with one notification and no other notification will load.

IMG_3AF15D2813FD-1

mstidham commented 4 years ago

Also noting that on Staging Version: 4.32.1 I see similar results however no infinite loader is displayed. I don't see any notifications and I'm required to back out and return to get any notifications to display on the Request tab. This is reproduced by the steps above.

bengtan commented 4 years ago

@mstidham:

I tried reproducing but unsuccessful so far. It might be account data specific.

Are you able to reproduce this on a Staging bypass account or a Production 'firebase test number' acccount?

mstidham commented 4 years ago

@bengtan I was just able to reproduce this issue on bypass account testytester (191-9191) on Staging.

bengtan commented 4 years ago

I was just able to reproduce this issue on bypass account testytester (191-9191) on Staging.

Hmmm ... I tried to reproduce on Staging with testytester.

Unsuccessful on iOS simulator. Successful on a real phone but only if I tap Menu » Updates » Requests immediately. If I dally before tapping, it doesn't not reproduce.

Interesting ...

bengtan commented 4 years ago

I can reproduce it on a real phone under XCode debugging. Doesn't always happen, but most of the time, it does.

But I'm not sure what's happening. Need to do more debugging and more pondering.

@mstidham: Can you try to reproduce on a firebase test number on Prod? It's possible that the Staging symptoms and Prod symptoms are from two different causes. I'd like to try to reproduce it on Prod too.

mstidham commented 4 years ago

@bengtan On prod with firebase test number (650-555-0004) is where I'm seeing the No new requests when going directly to the Requests tab. I then back out and return and have notifications.

bengtan commented 4 years ago

On prod with firebase test number (650-555-0004)

On prod, I can also reproduce but I see the same observations as Staging ie. no infinite loader. So I'm not sure if I'm seeing the same thing as the OP but I guess we'll find out.

I have a fix that I will submit shortly.

Diagnosis:

The Updates and the Requests tabs are, underlying, actually the same list. By default, the paged list component doesn't allow two queries to happen at the same time. If a query is issued when another is running, the second query is a no-op and it waits for the results of the first query.

In the case of the Updates and the Requests tabs, what happens is this:

mstidham commented 4 years ago

Staging Version: 4.32.2

I'm unable to test this issue due to app crash noted on #4458

mstidham commented 4 years ago

Verified on Staging Version: 4.32.3

mstidham commented 4 years ago

Verified on Prod Version: 4.32.3