Troubleshooting Guide: Resolving Screen Loading Issues

Overview

Screen loading issues can occur if the app is unable to initialize, data is stuck in cache, or conflicts arise from custom CSS/JavaScript. Common symptoms include endless spinning loaders, missing spinners, or login redirect failures. This guide provides step-by-step solutions to refresh the app, clear cache/cookies, debug custom code, and resolve persistent login problems.

Q1: Why does the loader keep spinning without any progress?

A1:
An endless spinning loader usually means the app cannot load properly due to network issues, server delays, or cached data.

How to Fix:

• Look for a “Click Here to Refresh” prompt, if available.

• Click the button to refresh the page and clear cache automatically.

• If no button appears, manually refresh the page (Ctrl + F5 on Windows or Cmd + R on Mac).

Q2: What should I do if my custom CSS or JavaScript is interfering with the loading spinner?

A2:
Custom CSS or JS may conflict with the loader, causing it to display incorrectly or disappear.

How to Fix:

• Review your custom CSS/JS for conflicts with loader classes or event handlers.

• Ensure styles aren’t overriding the loader’s default classes.

• Debug using your browser’s Inspect tool to identify problem code.

Q3: How can I manually clear site data if the refresh button isn’t working?

A3:
Clearing site data and cookies can fix persistent loading issues.

Steps:

1. Right-click → Inspect → open the Application tab.

2. Under Storage, click Clear Site Data.

3. Click the lock icon next to the URL → Cookies → remove site cookies.

4. Refresh manually (Ctrl + F5 on Windows, Cmd + R on Mac).

Q4: How do I know if the app is initializing or fetching fresh data?

A4:
The loader’s behavior indicates its state:

• Initializing: Spins when the app or a new page is starting up.

• Fetching Data: Spins again when refreshing or retrieving new information.

Wait for the loader to stop spinning to confirm the page/data is fully loaded.

Q5: What should I do if loading issues persist after troubleshooting?

A5:
If issues continue:

• Check your internet connection for stability.

• Contact support to see if there are server-side issues.

• If using custom code, revert recent CSS/JS changes.

• When contacting support, provide details on errors and steps you’ve already taken.

Q6: What should I do if I can’t log in after entering the code and the page doesn’t redirect?

A6:
This is usually caused by blocked cookies.

Steps to Fix (Google Chrome):

1. Look for the small paint icon with a red cross in the top-right corner.

2. Click the icon → switch to “Always allow” cookies for this site.

3. Click Done and refresh the page.

Once cookies are allowed, the login redirect should work properly.