Skip to content

AppCheck updates not taking effect in browser #2565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 tasks done
mackaby opened this issue Mar 20, 2024 · 3 comments
Closed
3 tasks done

AppCheck updates not taking effect in browser #2565

mackaby opened this issue Mar 20, 2024 · 3 comments

Comments

@mackaby
Copy link

mackaby commented Mar 20, 2024

Has your issue been reported?

  • I have searched the existing issues and confirm it has not been reported.
  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

After setting incorrect AppCheck keys for web, and trying to update the keys, it is not working instantly. I would assume that it is due to token expiry (if set to a few days in firebase it is problematic if there is an issue).

Expected Behavior

When keys are updated, it should take effect even if the user has used the app before. Is there a way to trigger token refresh if keys are updated?

Steps to Reproduce

Change the appcheck keys and see if it has any effect on your verification. Clearing cookies, cache etc wont work).

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITFXkfLluJNPjMRE15fUdMExiiAwGUwbUOc7j9VEGAsjCeP1OrAuOczeaRdWWOqHYwl2IFb+rH8dw+z0ht7mGPI3FweabNg++YdpUxDvWme6R5iJEpOofWgnDeVYGFyy0aWrph0nPutaLkEj2EOAB+yua3qCf9qOYwx5e6fDbOY=

Context

Trying to improve security by using AppCheck. Impact is that something is done wrong in the setup, it will take time for users to get an updated appcheck connection.

Visual documentation

Additional Info

No response

Environment

- FlutterFlow version: 4.1.33
- Platform: web
- Browser name and version: chrome 122.0.6261.129
- Operating system and version affected: macOS Sonoma 14.4
@mackaby mackaby added the status: needs triage A potential issue that has not been confirmed as a bug. label Mar 20, 2024
Copy link

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

Copy link
Collaborator

Hey @mackaby thanks for your report. Is you experience with AppCheck still not the expected, or has it been fixed on the newer versions of FF?

@ignalauret ignalauret removed the status: needs triage A potential issue that has not been confirmed as a bug. label Apr 11, 2024
@leighajarett
Copy link
Collaborator

Closing this issue since we haven't heard back from you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants