Known Bugs
We prioritize transparency. Below are the current known issues on the platform, our timeline for resolving them, and a record of recently resolved issues.
Active Issues (1)
Language Selection Resets on Hard Refresh (Rare)
Target Fix
v4.0.x
Description
In some browser configurations with strict privacy settings or storage partitioning (e.g., Firefox strict mode), the selected language may not persist across full page reloads because access to localStorage is blocked.
Workaround
Use a browser that supports localStorage, or set your browser's privacy level to Standard. The language switcher functions correctly on first selection within the session.
Recently Resolved
Curriculum Consistency Upgrade
Target Fix
v4.3.0 ✓
Description
Previous tracks lacked a unified progression structure, making it difficult for absolute beginners to find an entry point.
Resolution
Fixed in v4.3.0 — All 11 core tracks restructured into a 3-Tier model (Foundations, Intermediate, Production) and a new 'Foundations' track added.
Functional PWA Installation Engine
Target Fix
v4.3.0 ✓
Description
The previous PWA prompt was only informational and did not trigger a native installation event.
Resolution
Fixed in v4.3.0 — Introduced usePwaInstall hook and connected it to the native 'beforeinstallprompt' event.
Terminal Scrolls Entire Page on Load
Target Fix
v4.0.0 ✓
Description
The interactive terminal on the landing page used `autoFocus` and `scrollIntoView`, which caused the browser to scroll the whole page down to the terminal input on initial load, hiding the hero section. Additionally, when users typed commands, the scrollIntoView call hijacked the page scroll container.
Resolution
Fixed in v4.0.0 — autoFocus removed; scroll is now contained within the terminal element.
Mobile UI Lag Smoothing
Target Fix
v4.2.0 ✓
Description
Heavy backdrop blurs on mobile sidebars caused extreme spikes in DOM repaints, lagging the device.
Resolution
Fixed in v4.2.0 — Conditionally removed backdrop-blur-sm on mobile viewports (<768px).
3D Hero Stutter on Low-End Devices
Target Fix
v4.1.0 ✓
Description
On some older mobile devices, the 3D scene may cause frame drops despite existing DPR clamping.
Resolution
Fixed in v4.1.0 — The 3D Canvas is completely disabled on mobile viewports (<768px) to guarantee smooth 60FPS performance, falling back to a CSS-based blurred element.
Found something else?
Report new issues directly on our GitHub repository. We welcome community audits.
Need live support?
Follow our Instagram page and message us for immediate help.