vodafone-website / docs/known_issues.md

known_issues

Last updated: 4/16/2026GitHubVodafone website

Known Issues

This template will be used for each known issue. To keep formatting consistent.

[EXAMPLE] Login Token Refresh Fails in Background on Android

  • Description:
    On certain Android devices, the Expo app does not refresh authentication tokens in the background. This leads to users being logged out unexpectedly after token expiration.

  • Steps to Reproduce:

    1. Login to the app on an Android 10+ device
    2. Leave the app idle in the background for 15+ minutes
    3. Open the app again and attempt any authenticated action
    4. Receive a 401 Unauthorized error due to expired token

  • Expected Behavior:
    The token refresh job should run in the background and renew the session.

  • Actual Behavior:
    The background task is either killed by Android OS battery optimizations or never scheduled correctly. Token is not refreshed and the session expires.

  • Environment:

    • OS: Android 11
    • Browser/App: Expo Go v53
    • Device: Samsung Galaxy A51

  • Workaround (if any):
    Add a foreground-safe token refresh mechanism using AppState listeners to refresh on resume.

  • Demo Instructions:
    Login on an Android device, switch apps for 15 minutes, return to the app and attempt a protected API call.

  • Tracking:
    GitHub Issue #1

  • Status:
    In Progress

Issue Title Here

  • Description:
    Briefly describe what the problem is and when it happens.

  • Steps to Reproduce:

    1. Step-by-step actions to trigger the issue
    2. Make it reproducible when possible

  • Expected Behavior:
    What should happen instead.

  • Actual Behavior:
    What actually happens, including any error messages or screenshots.

  • Environment:

    • OS: (e.g., Windows 11, Android 13, etc.)
    • Browser/App: (e.g., Chrome v122, Expo Go v53, etc.)
    • Device: (e.g., iPhone 14 Pro, Pixel 7, MacBook M1)

  • Workaround (if any):
    Temporary fix or mitigation.

  • Demo Instructions:
    How to safely demo the bug (test account, staging link, etc.).

  • Tracking:
    GitHub Issue #123

  • Status:
    (e.g., Open, In Progress, Blocked, Fixed in vX.Y.Z)