How to handle concurrent performAction calls?
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
We have a project which can fire off multiple API calls concurrently. Each request calls performAction and in some cases this results in the same refresh token being used more than once and sometimes this is rejected by the server.
Is there a standard way to handle this issue or could the library be updated to handle this internally perhaps?
I have tried using semaphores and DispatchQueue but this doesn't work properly as the calls are async.
Contributor guide
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.
Research direction
Start by tracing the performAction entry point and the asynchronous refresh-token flow it invokes. Review the existing issue discussion to determine the expected behavior when concurrent calls share a refresh token. Done should include an agreed concurrency strategy and coverage showing that concurrent requests handle token refresh consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- api, authentication, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100