# [Bug] Error Report Form Requires Sign-In Despite Active Session in SpikerSoft Stacker #1203

Open
opened 2026-10-12 02:58:03 +00:00 by enjin2310 · 0 comments

Summary

In SpikerSoft Stacker, the error reporting feature incorrectly prompts users to sign in even when they are already logged into their account. The Send button becomes active once the minimum word count is met, but upon interaction, the system displays a message indicating that the user must sign in again. Despite this, the report is successfully submitted, suggesting a mismatch between the UI state and backend authentication logic.

Issue Description

When attempting to submit a bug report, the form displays the message “Your sign-in has expired — sign in again so this report counts toward the licence.” However, the top-right corner of the interface clearly shows the user as logged in. Clicking Sign in opens the account dialog confirming that the user is licensed and authenticated. Closing this dialog and returning to the report form leaves the Send button enabled, but the sign-in warning persists. The report still sends successfully, indicating that the authentication check is inconsistent between the UI and backend.

Environment

Property Value
Application SpikerSoft Stacker
Module Error Report / Account Authentication
Environment Production
Operating System Windows 11
Version v2026.10.10e
Device Desktop
Account enjin2310 (licensed and logged in)

Preconditions

User is logged into a valid licensed account.

Steps to Reproduce

  1. Launch SpikerSoft Stacker and ensure you are logged in.
  2. Open the Report a Bug form.
  3. Type enough text to enable the Send button.
  4. Observe the message: “Your sign-in has expired — sign in again…”
  5. Click Sign in and confirm that the account is active.
  6. Close the account dialog and return to the bug report form.
  7. Attempt to send the report.

Expected Result

  • The system should recognize the active session and allow report submission without showing the sign-in warning.
  • The Send button should function normally without redundant authentication prompts.

Actual Result

  • The form incorrectly displays a sign-in expiration message.
  • The Send button remains enabled but misleadingly suggests the user is logged out.
  • The report is still submitted successfully, indicating backend authentication works but UI validation fails.

Evidence

  • Image 1: Bug report form showing “Your sign-in has expired” despite active session.
  • Image 2: Account dialog confirming user is signed in and licensed.

Impact

  • Causes confusion for users submitting bug reports.
  • Reduces trust in the authentication system.
  • Minor functional issue but significant UX inconsistency.

Frequency

Always

Reproducibility

100%

Severity

Medium

Suggested Fix

  • Synchronize UI authentication state with backend session validation.
  • Refresh session tokens when the bug report form is opened.
  • Remove redundant sign-in prompts when the user is already authenticated.
  • Add a visual confirmation (e.g., “Report sent successfully”) to reassure users after submission.
## Summary In **SpikerSoft Stacker**, the error reporting feature incorrectly prompts users to sign in even when they are already logged into their account. The **Send** button becomes active once the minimum word count is met, but upon interaction, the system displays a message indicating that the user must sign in again. Despite this, the report is successfully submitted, suggesting a mismatch between the UI state and backend authentication logic. ## Issue Description When attempting to submit a bug report, the form displays the message **“Your sign-in has expired — sign in again so this report counts toward the licence.”** However, the top-right corner of the interface clearly shows the user as logged in. Clicking **Sign in** opens the account dialog confirming that the user is licensed and authenticated. Closing this dialog and returning to the report form leaves the **Send** button enabled, but the sign-in warning persists. The report still sends successfully, indicating that the authentication check is inconsistent between the UI and backend. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Stacker | | Module | Error Report / Account Authentication | | Environment | Production | | Operating System | Windows 11 | | Version | v2026.10.10e | | Device | Desktop | | Account | enjin2310 (licensed and logged in) | ## Preconditions User is logged into a valid licensed account. ## Steps to Reproduce 1. Launch **SpikerSoft Stacker** and ensure you are logged in. 2. Open the **Report a Bug** form. 3. Type enough text to enable the **Send** button. 4. Observe the message: “Your sign-in has expired — sign in again…” 5. Click **Sign in** and confirm that the account is active. 6. Close the account dialog and return to the bug report form. 7. Attempt to send the report. ## Expected Result - The system should recognize the active session and allow report submission without showing the sign-in warning. - The **Send** button should function normally without redundant authentication prompts. ## Actual Result - The form incorrectly displays a sign-in expiration message. - The **Send** button remains enabled but misleadingly suggests the user is logged out. - The report is still submitted successfully, indicating backend authentication works but UI validation fails. ## Evidence - **Image 1:** Bug report form showing “Your sign-in has expired” despite active session. - **Image 2:** Account dialog confirming user is signed in and licensed. ## Impact - Causes confusion for users submitting bug reports. - Reduces trust in the authentication system. - Minor functional issue but significant UX inconsistency. ## Frequency Always ## Reproducibility 100% ## Severity Medium ## Suggested Fix - Synchronize UI authentication state with backend session validation. - Refresh session tokens when the bug report form is opened. - Remove redundant sign-in prompts when the user is already authenticated. - Add a visual confirmation (e.g., “Report sent successfully”) to reassure users after submission.
Sign in to join this conversation.