Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report: Inconsistent User ID Across Devices and Browsers #186

Open
Professor-Chen opened this issue Dec 12, 2024 · 0 comments
Open

Bug Report: Inconsistent User ID Across Devices and Browsers #186

Professor-Chen opened this issue Dec 12, 2024 · 0 comments

Comments

@Professor-Chen
Copy link

Bug Report: Inconsistent User ID Across Devices and Browsers

Description

Users have reported that their Prover ID differs across devices and browsers, even when using the same email address to log in. As a result, the cumulative points or contributions are not synchronized, leading to fragmented user data.

Issue Details

Observations

  • Different Devices: Logging in with the same email on multiple devices generates different Prover IDs.
  • Different Browsers: Using the same email on different browsers on the same device also results in different Prover IDs.

Impact

  • Points earned on one device/browser do not reflect when switching to another device/browser.
  • Users cannot accumulate their efforts into a single Prover ID, leading to frustration and inefficiency.

Steps to Reproduce

  1. Log in with the same email address on Device A, Browser 1.
  2. Observe the Prover ID generated.
  3. Log in with the same email address on Device B, Browser 2.
  4. Compare the Prover IDs and accumulated points between the two sessions.

Expected Behavior

The Prover ID should remain consistent across all devices and browsers when the same email is used, ensuring synchronized cumulative points.

Actual Behavior

A unique Prover ID is generated for each device or browser, preventing point synchronization.

Suggested Fixes

  1. Centralized Prover ID Management:

    • Ensure the backend ties the Prover ID to the user’s email or account.
    • Synchronize Prover ID across all sessions initiated with the same email.
  2. Session Handling:

    • Use persistent cookies or tokens to maintain session continuity across browsers and devices.
  3. Account Linking:

    • Implement a mechanism for users to link Prover IDs manually if multiple IDs have already been generated.
  4. Debugging Tools:

    • Add detailed logs to identify why new Prover IDs are generated instead of reusing existing ones.

Additional Context

This issue undermines user confidence in the system and discourages participation. Resolving it will enhance user satisfaction and engagement.


Please investigate and resolve this inconsistency to improve the user experience and ensure seamless point accumulation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant