I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

I experience the same issue. In my case the exchangeDebugToken is requested multiple times in close succession.
https://content-firebaseappcheck.googleapis.com/v1beta/projects/{projectId}/apps/{appId}:exchangeDebugToken?key={apiKey}

Resulting in the following error:

FirebaseError: AppCheck: Fetch server returned an HTTP error status. HTTP status: 429. (appCheck/fetch-status-error)

When the request does succeed, I get the response containing the attestationToken and the ttl of 3600s. Seeing that the request is executed multiple it seems the ttl might not be considered correctly.

Can you describe how you are using App Check? Are you using debug mode like the Stack Overflow question or something else? Also which products are you using it with? Functions? Storage? Realtime Database? Can you show the code for what you are doing with each of those?

I am using the debug mode yes. I am also using angular and I am initialising it like the chosen answer in this stackoverflow question

https://stackoverflow.com/questions/67908846/how-to-initialise-firebase-app-check-in-angular

I am using it with Functions, Storage and Realtime Database and they all throw the errors. Occassionally some requests get through and say a storage getDownloadLnk requests works but 99% of the time there will be at least 1 429 error when the page is loaded.

I have added the debug token generated by the library (also that was hard to find as it only seems to print once then stops logging it as its in local storage.. had to debug the minified code to get it)

Any help is really appreciated as this is blocking my local development.

I think this may be caused because if you are in debug mode, the App Check token is not cached, and instead it hits the App Check exchange endpoint on every request. That would be a bug on our part and I'll look into fixing it.

Thanks a lot 😄

Hi is there any update with this?

This has just been merged. It missed the cutoff for this week's release but should be released next week.