Blank Page Rendering When Accessing Older Links in Arc Sphere App

While testing the ArcBlock Arc Sphere app, I noticed an issue specifically related to how older links are rendered when accessed from within an active session. When I click on certain older links (for example, older posts or reports), the page fails to display any content and instead loads into a completely blank/black screen.

Interestingly, this issue only occurs if the link is opened directly within the current session. However, when I refresh the page multiple times, the problem still persists. On the other hand, if I copy the same link and open it in a new tab, the page loads correctly without any issue.

This strongly suggests that the bug is related to how the Arc Sphere container handles routing and session state inside its embedded webview. It appears that the app fails to properly re-render older content when accessed from an existing session, possibly due to cached state, expired session tokens, or incomplete route handling. The fact that a clean/new tab session resolves the problem points toward session persistence and rendering flow inside Arc Sphere being the root cause.

From a user perspective, this behavior is confusing because it creates the impression that the older links are broken or missing. Instead of displaying a blank page, the app should either:

Correctly refresh and re-render the requested content, or

At minimum, display an error message or fallback UI to inform the user that the content cannot be displayed.

This bug reduces trust in the platform’s reliability, especially for users who are revisiting older content, bug bounty reports, or community discussions. Since Arc Sphere is meant to be a gateway to ArcBlock’s ecosystem, ensuring that all links — old or new — render properly in-app is important for maintaining user experience and engagement.