[Bug] useAuth hook calls getAccessToken on every streaming connection — N token reads for N streams

[RUKAYAT-CODER]

Overview

src/hooks/useStreamingData.ts (and callers in video, quiz, and course modules) calls getAccessToken() from secureStorage.ts independently for each streaming connection. getAccessToken reads from expo-secure-store, which involves a native bridge call. Under normal usage with 3 concurrent streams (video + progress + notifications), this results in 3 sequential native bridge calls per token read cycle (token is read on reconnect, on retry, and on each new stream).

Specifications

Features:

• Token cached in memory for 60-second window (refreshed when approaching expiry)
• All streaming connections share the same in-memory token cache
• Cache invalidated on token refresh or logout

Tasks:

• Add in-memory token cache in src/services/secureStorage.ts: { token: string, expiresAt: number } | null
• getAccessToken() returns cached value if Date.now() < expiresAt - 30000
• Cache cleared in clearTokens() and saveTokens()
• Add unit test confirming single SecureStore read for 3 rapid getAccessToken() calls
• Cache TTL configurable via constant

Impacted Files:

• src/services/secureStorage.ts

Acceptance Criteria

• 3 calls to getAccessToken() within 1 second result in 1 native bridge call
• Cache is invalidated after saveTokens() or clearTokens()
• Cache TTL default is 60 seconds
• Unit test confirms single SecureStore.getItemAsync invocation for 3 rapid calls

[Dagdon]

@Dagdon has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, please can I work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dagdon to this issue.

[abdulrcrtw]

@abdulrcrtw has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this task.

(and callers in video, quiz, and course modules) calls from independently for each streaming connection. reads from , which involves a native bridge call. Under normal usage with 3 concurrent streams (video + progress + notifications), this results in 3 sequential native bridge calls per token read cycle (token is read on reconnect, on retry, and on each new stream).

I've reviewed the repo and understand the codebase. I can deliver a clean implementation covering all acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abdulrcrtw to this issue.

[drips-wave]

Congratulations, @abdulrcrtw! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @abdulrcrtw: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊