Access token might be inconsistent across threads

Open
#378 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
firebase, python
Domain
api, authentication

Research direction

No source file, test, or entry point is identified in the report. Trace how v2.0.x issues and stores access tokens and shares credentials across threads, then reproduce concurrent refresh and read scenarios. Done means token handling remains consistent across threads without redundant refreshes or stale credentials.

Written by the indexing model from the issue text.

Description

In v2.0.x, access tokens are issued per thread. However, credentials are shared. This can lead to inconsistencies in access tokens between threads. Specific issues that can occur are as follows:

  • Token refreshes occur as many times as the number of threads.
  • Credentials are shared, so when multiple threads simultaneously refresh or read a token, it may become outdated.
Dominant language
Python
Stars
814
Forks
209
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from olucurious/PyFCM

All issues in olucurious/PyFCM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.