useIdTokenResult forceRefresh not working?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- firebase, nextjs, react, typescript
- Domain
- authentication, frontend
Research direction
Start by reproducing the difference between Firebase user.getIdTokenResult(true) and ReactFire's useIdTokenResult(user, true) across the described Next.js page navigation. Compare the claims returned before and after router.push("/newpage"); done means the hook exposes the updated claim rather than the old one.
Written by the indexing model from the issue text.
Description
Version info
React: 17 experimental with suspense
Firebase: 8.6.2
ReactFire: 3.0.0-rc.0
Other (e.g. Node, browser, operating system) (if applicable):
Test case
I am using nextjs and reactfire. I am setting auth claims on one page and using the normal query, I get new claims. Afterwards I switch the page.
let token = await user.getIdTokenResult(true)
console.log(token.claims) // { claim: NewClaim }
router.push("/newpage")
Now on the new page, I can get the new claims via the above command and it shows me the new claim, too.
However, using the reactfire hook, I am still getting old ones:
const { data: token} = useIdTokenResult(user, true);
console.log(token.claims) // { claim: OldClaim }
Expected behavior
Normally the useIdTokenResult should give back the updated claim.
Actual behavior
The useIdTokenResul keeps showing the old claim.
What I am trying to achieve is a claim update as described in the experimental firebase extension Auth Claims: https://github.com/FirebaseExtended/experimental-extensions/blob/next/firestore-auth-claims/POSTINSTALL.md#activating-new-custom-claims
- Dominant language
- TypeScript
- Stars
- 3.6k
- Forks
- 403
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 10
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FirebaseExtended/reactfire
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
FirebaseExtended/reactfire#801 ·
-
v5
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FirebaseExtended/reactfire#793 ·
-
v5
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FirebaseExtended/reactfire#790 · 2 comments ·
-
v5
Difficulty 4/5 3-5 days Newbie friendliness 55/100
FirebaseExtended/reactfire#789 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
FirebaseExtended/reactfire#788 ·
All issues in FirebaseExtended/reactfire
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Fission-AI/OpenSpec#1986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nestjs/docs.nestjs.com#3554 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
publicodes/publicodes#868 ·
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 78/100
EclipseFdn/open-vsx.org#13488 ·
Maintainers usually reply within 2 days