Users can sometimes get a white screen when logging into the Bloom application. Once logged in, the screen will show the Perspective but within a few seconds will turn white with no ability to navigate the page.

After capturing the Bloom debug logs, in the bloom_application_log.txt you will see errors similar to the following:

2023-09-08 10:29:41.672 ERROR code: undefinedTypeError: Cannot read properties of undefined (reading 'palette')
at eJn (http://<address>:7474/bloom/assets/index-3921b0fa.js:387:106590)

How to solve this problem?

The easiest fix for the user is to delete the Scene that the user is accessing when the error occurs. If using the Bloom Server Plugin, clearing local cache will not help in this case as Perspectives and Scenes are stored in the database. The only way to clear those is by deleting them in the database.
 

Start by finding the offending Scene id by looking in the bloom_application_log.txt, and locate the scene query causing the error

2023-09-08 10:29:41.441 DEBUG readTransaction query 55c35494-7ccf-4b12-ab5e-daa5c3ecf66e 
MATCH (s:`_Bloom_Scene_`)
WHERE s.id = $id
RETURN s
{"id":"cd7791b0-4c64-11ee-8a5a-77a33861f650"}
2023-09-08 10:29:41.442 DEBUG Async session successfully closed
2023-09-08 10:29:41.672 ERROR code: undefinedTypeError: Cannot read properties of undefined (reading 'palette')

If the user is not using the Scene or does not need it, the easiest solution is to just delete the offending Scene by using the Scene id located previously.

MATCH (s: _Bloom_Scene_ { id: 'cd7791b0-4c64-11ee-8a5a-77a33861f650' }) DETACH DELETE s;

Improvements have been made in this area in Bloom versions 2.10 and higher. The latest Bloom Release Notes and versions can be found at https://neo4j.com/release-notes/bloom .