Ramsay

@russellwheatley @MarkDuckworth The [initial problem](https://youtube.com/shorts/Fq67pKY0yDo?feature=share) I faced was that after resuming the app after an extended period (a day or two), all long-lived snapshots would stop updating, even though new...

In my most recent Android app release, I've introduced code that detects the 'Permission Denied' error upon app resume and prompts the user to re-login to rectify the situation. While...

> I attempted to reproduce this week with my own app, but did not have success. I'm tweaking some things and continuing to try. To reproduce this issue, imagine an...

I will start working on a reproduction this week. In my live app I had to resort to measures such as extending the token lifetime significantly alongside code hacks I...

@russellwheatley @puf @MarkDuckworth **Here it is:**  I've created a Minimal, Complete, and Verifiable Example (MCVE), and within four hours of launching the app (in release mode with Play Integrity...

I've created a [repo](https://github.com/RamsayGit/firebase-token-refresh-mcve) and sent you an invitation. A significant part of the setup needed to recreate the error resides within the Firebase project, not the code. I will...

> I didn't realize this involves App Check. When you say, "App Check must be enforced for Firestore with Play Integrity", does that mean you only see this when using...

@MarkDuckworth Can I please be informed of the current status of this bug?

@MarkDuckworth After further testing with the MCVE project I'm almost certain the issue is directly related to Appcheck since I could not replicate the error with Appcheck turned off. When...

@MarkDuckworth I did not see any error messages regarding this issue other than the 'caller does not have permission...' error. I did implement many workarounds to help mitigate this issue...