“The heatmap could not start” with EvalError (unsafe-eval): fixed in 0.46.0

What you see

A notice titled “The heatmap could not start” with “The chart for {symbol} failed to initialise.” Under “Technical detail”, the error starts with “EvalError: Evaluating a string as JavaScript violates the following Content Security Policy directive because 'unsafe-eval' is not an allowed source of script”. The status line reads “{symbol} · could not start”. It happened on the Heatmap page and in heatmap tiles of My pages alike.

Why it happens

The WebGL library the heatmap used wrote JavaScript for its drawing commands and evaluated it at start-up. The application’s Content Security Policy keeps a bare script-src 'self' on purpose, enforced by a test, and allows evaluation only inside the scripting sandbox. The development environment has no such policy, which is why the heatmap worked in development and not in the installed app. The same cause had already been removed from the 3D GEX surface in 0.30.0.

Version 0.46.0 draws the heatmap with direct WebGL calls for its two programs (the liquidity map and the bubbles), without any generated code.

How to fix it

• Update to 0.46.0 or later: accept the update prompt at startup, or install it from Account → Versions.
• If you pinned an older version, click “Resume automatic updates” on the Versions card, or install 0.46.0 directly.
• After updating, open the heatmap again; the Retry button of the notice also rebuilds it.

What it is not

• Not a graphics driver or GPU problem: the error comes from the security policy, not from WebGL.
• Not a data problem: the book may be arriving fine while the renderer refuses to start.
• Not something to fix by relaxing security settings: the fix is in the app.

When to contact support

When none of this helps, write to support through Menu → Report a problem or on the Senzoukria Discord. If you are on 0.46.0 or later and still see “could not start”, copy the Technical detail and your graphics card model.