Skip to content

feat(appcheck): getTokenResult - #18492

Merged
Lyokone merged 3 commits into
mainfrom
feat/8970-2
Jul 30, 2026
Merged

feat(appcheck): getTokenResult#18492
Lyokone merged 3 commits into
mainfrom
feat/8970-2

Conversation

@Lyokone

@Lyokone Lyokone commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Description

Adds a non-breaking getTokenResult() API that returns an AppCheckTokenResult containing the token and its expiration time, while preserving the existing getToken() string API and wire contract. Android, Apple, and Windows populate expiration metadata from their native SDKs; on web, expirationTime is null because the public Firebase JavaScript SDK only exposes the token string.

final result = await FirebaseAppCheck.instance.getTokenResult();

print(result?.token);
print(result?.expirationTime);

Related Issues

Local Verification

  • flutter test passed for firebase_app_check and firebase_app_check_platform_interface.
  • Chrome tests passed for firebase_app_check_web.
  • flutter analyze passed for the public, platform-interface, web, and integration-test packages.
  • The Android example compiled successfully with flutter build apk --debug --android-skip-build-dependency-validation.
  • The iOS simulator build was blocked while resolving dependencies by an unrelated Xcode SwiftPM internal exception.

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@gemini-code-assist

Copy link
Copy Markdown
Contributor
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

@demolaf demolaf left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, there's a lint issue on CI.

@Lyokone
Lyokone merged commit 361f719 into main Jul 30, 2026
40 of 45 checks passed
@Lyokone
Lyokone deleted the feat/8970-2 branch July 30, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 [firebase_app_check] .getToken() should return a AppCheckToken class

3 participants