Bug: Theme Settings Fails to Save Changes – "No Token Provided, Please Try Again"

[Sargam-Ghagre]

Description

The Theme Settings page is unable to save the selected primary color. When clicking the Save Theme Changes button, the request fails and displays the following error message:

"No token provided. Please try again."

As a result, users cannot save or update their theme preferences.

Steps to Reproduce

1. Navigate to the Theme Settings page.
2. Select a primary color.
3. Click Save Theme Changes.
4. Observe the error message.

Expected Behavior

The selected theme color should be saved successfully, and the updated theme should be applied without any errors.

Actual Behavior

The application displays:

"No token provided. Please try again."

and the theme changes are not saved.

Possible Cause

• Authentication token is not being sent with the API request.
• Token is missing or expired.
• Theme settings API is rejecting unauthenticated requests.
• Frontend is not retrieving or attaching the token correctly.

[SahilSolve02]

/assign

[github-actions]

Hi @SahilSolve02, please wait 6h before claiming this issue again (cooldown active).

[ankurkrgupta22122006-oss]

@aryandas2911 please assign this issue to me

[GeethaBurigalla]

/assign

[github-actions]

Hi @GeethaBurigalla, please wait 6h before claiming this issue again (cooldown active).

[aaniya22]

pls assign this to me under gssoc

[karrisanthoshigayatri]

Hi @aryandas2911, I'd like to work on this issue under GSSoC'26.

Approach:

• Investigate why the authentication token is missing in the theme update request.
• Ensure the token is correctly retrieved and attached to the API call.
• Verify theme changes are saved successfully and handle token-related errors gracefully.

Kindly assign this issue to me. Thank you!

[Sargam-Ghagre]

/assign

[github-actions]

Hi @Sargam-Ghagre, please wait 6h before claiming this issue again (cooldown active).

[Rashmi2806525]

hy @aryandas2911 i would like to solve this issue , assign it to me

[Sargam-Ghagre]

/assign

[github-actions]

Hi @Sargam-Ghagre, please wait 6h before claiming this issue again (cooldown active).