No Message String... warning in console

[stclairdaniel]

Describe the bug

In a minimal Blockly use case with a simple toolbox, warnings of the following type appear in the console:

No message string for %{BKY_MATH_ONLIST_TOOLTIP_STD_DEV} in %{BKY_MATH_ONLIST_TOOLTIP_STD_DEV}
No message string for %{BKY_MATH_ONLIST_TOOLTIP_RANDOM} in %{BKY_MATH_ONLIST_TOOLTIP_RANDOM}
...

To Reproduce

1. Visit this minimal reproduction example and view the console

Expected behavior

No warnings in the console

Screenshots

Desktop (please complete the following information):

• OS: MacOS Catalina 10.15.6
• Browse: Chrome 85.0.4183.121 (Official Build) (64-bit)
• Version: "blockly": "3.20200924.3",

[moniika]

I think this is the same issue that is happening in #4358. I will close that one in favor of easier repro steps described here.

Based on investigation on that issue already done by @oleggo, Blockly.utils.checkMessageReferences is run after page load and in some environments the Blockly.Msg table is not yet loaded.

blockly/core/extensions.js

Line 415 in 11987dc

Blockly.utils.checkMessageReferences(msgTemplate);

[oleggo]

@moniika it happens in the case when Blockly main module starts to load AFTER document.readyState is set to 'complete'. It causes Blockly.utils.checkMessageReferences to be called immediately without waiting for current tick to finish, because of this code:

blockly/core/utils.js

Line 486 in 11987dc

fn(); // Page has already loaded. Call immediately.

One possible scenario is when Blockly is loaded under Webpack.

[becnealon]

Has this issue been fixed? I am still able to recover this error. Is there a recommended solution?

Desktop (please complete the following information):
OS: MacOS Big Sur 11.2.3
Browse: Chrome 87.0.4280.141 (Official Build) (arm64)
Version: "unpkg" 6.20210701.0 as well as "github/blockly" 7.20211209.0

[johnnyoshika]

I'm also interested in this issue. It started to appear when I split my React app using code splitting. Here's the relevant discussion on Google Groups: https://groups.google.com/g/blockly/c/VQ1qjKMe3m4/m/Z-s_T2vrEQAJ

[dojo-coder]

I am also facing this issue. Does anyone know how to fix this?

[stnor]

Also having the issue. I'm using lazy loading with:

const Blockly = await import('blockly/browser');

[johnnyoshika]

@stnor That seems consistent with the problem I'm having. Although these warnings are annoying, they haven't been a problem for my app so far.

[alexbk66]

It also causes "screenshader.js:80 Uncaught Error: Tooltip function must return a string"

I don't do anything special, just load html with a simple Blockly example. Getting lots of warnings.

[EDIT]

Just noticed, all warning I'm getting are about TOOLTIP. if it helps...

No message string for %{BKY_TEXT_APPEND_TOOLTIP} in %{BKY_TEXT_APPEND_TOOLTIP}
No message string for %{BKY_MATH_ARITHMETIC_TOOLTIP_ADD} in %{BKY_MATH_ARITHMETIC_TOOLTIP_ADD}

[BeksOmega]

Hello all! Sadly I'm not sure that this is something the core team can fix on our end :/ The issue is that Blockly's translation files need to be loaded before Blockly is loaded, which (as far as I can tell) is related to how Blockly gets webpacked/rolledup along with the rest of an application.

If you run into this issue, the only thing I can recommend (at the moment) is digging into how your architecture handles loading, to make sure that message files get loaded before the rest of Blockly.

If anyone has information about how the core team could ensure this from our end, we would love more information =)

[johnnyoshika]

I'm using Create React App, which does the loading using its pre-configured webpack settings. Create React App is pretty popular, so I imagine this will be a common problem with Blockly. That said, these warnings haven't been a problem other than the annoying console messages, so it's something I'm willing to live with.

[alexbk66]

I'm using Create React App, which does the loading using its pre-configured webpack settings. Create React App is pretty popular, so I imagine this will be a common problem with Blockly. That said, these warnings haven't been a problem other than the annoying console messages, so it's something I'm willing to live with.

But if you hover the mouse over the blocks - when it tries to display the Tooltip - doesn't it fail because the messages are not loaded?

[johnnyoshika]

@alexbk66 Is this the tooltip you're referring to? Seems to work for me:

[maribethb]

Hi everyone,

We submitted a fix for a related issue and I'm hoping it may have helped this, but since we don't use Angular or React ourselves it would be great to hear from you. Could you try this beta version 8.0.1-beta.0 and see if this issue is resolved? Thanks!

[DBurkeAoE]

Hello, I just recently started a project using Blockly in Angular and was running into this issue when using version 8.0.0 but updating to the version 8.0.1-beta.0 was able to fix the problem. However when updating to version 8.0.1 that just released the problem returned so I had to go back to the beta version. Was the fix intentionally removed in the stable release for 8.0.1 and if so can we expect it in a future stable release?

[maribethb]

Thanks for confirming that the beta patch fixed the issue in Angular! We hadn't been able to confirm that before so that is great to hear.

Unfortunately the patch we applied to fix it for this case broke using setLocale for those using multiple translation files, so we didn't include that patch in the latest beta. We aim to have a complete fix (for both use cases) before our next main release and we can likely put out a patch fix for this issue when we have one. You can follow along at #6123 for more details. Thanks!

[reedspool]

I am having this issue as well without a build step. I did npm install blockly today and have version 8.0.2. I serve my application simply with npx serve. This is how I am loading Blockly at the end of my <body /> tag:

        <script type="text/javascript" src="./node_modules/blockly/blockly_compressed.js"></script>
        <script type="text/javascript" src="./node_modules/blockly/msg/en.js"></script>
        <script type="text/javascript" src="./node_modules/blockly/javascript_compressed.js"></script>
        <script type="text/javascript" src="./node_modules/blockly/blocks_compressed.js"></script>

Unfortunately I'm not able to find the beta branch or release package to test if that would fix it.

If I move msg/en.js above blockly_compressed.js then I get this error followed by the list of tooltip message warnings:

en.js:8 Uncaught TypeError: Cannot set properties of undefined (setting 'Msg')
    at en.js:8:22
    at en.js:10:2

[adrianfung]

I use version 8.0.2 too.
I removed the node_modules/blockly/msg and use the GitHub's msg,
and then changed the script src to ./node_modules/blockly/msg/js/en.js

[johnnyoshika]

@BeksOmega I tried blockly@8.0.4-beta.0 and it results in this compile error which prevents my React app from loading:

This error doesn't occur in blockly@8.0.3-beta.1 so I believe it's a regression.

I hope that's helpful.

[maribethb]

Thanks Johnny. We have the latest fix at 8.0.4-beta.1 and it seems to be working in all the tests we've thought to run so far. would greatly appreciate you taking another look!

[johnnyoshika]

@maribethb I just tried 8.0.4-beta.1 and unfortunately I still get the string warnings:

My environment is described here: https://groups.google.com/g/blockly/c/VQ1qjKMe3m4/m/DmoPBv7RDgAJ

If it'll be helpful, I can create a simple React repo with code splitting to reproduce the warnings.

[Gauntlet173]

I'm having a similar problem, with warnings on load, and the main visible issue being that the block context menus will no longer display because Msg is undefined at contextmenu_items.js at 570.

I just tried it using 8.0.4-beta.1 and it did not resolve the problem.

[Gauntlet173]

I have reverted Blawx to github's v8.0.2 and created a local copy of the 8.0.4 version of the en.js file, and loaded it as suggested above by @adrianfung and @jasonpanelli. That seems to be working.

[Insood]

Hey all, I've been using <script src="https://unpkg.com/blockly/blockly.min.js"></script> and it used to work until 8.0.4.

Downgrading to 8.0.3 fixes this for me: <script src="https://unpkg.com/blockly@8.0.3/blockly.min.js"></script>

I've tried specifying 8.0.4-beta.1, but the issue still persists in that version.

I recommend bundling a specific version in your app :)

[maribethb]

@Insood can you provide more information? How did 8.0.4 break for you and how are you loading the message files?

In particular if you were using one of the workarounds listed here where you used an older version of the msg files with v8.0.3 then I think if you remove the workaround and use the version packaged in the release then everything should work... but if there's a test case we missed and 8.0.4 is broken for you we'd like to know asap. Thanks!

[Gauntlet173]

Just as follow up, #6329 seems to have solved the problem for me. If I remove the workaround, and clone from the "develop" branch of the repository, it seems to be resolved.

[maribethb]

Thanks for confirming! I believe most of the recent comments on this thread were really about #6123 and have accordingly marked that issue as closed.

Unfortunately that issue looked similar in effect to this one, but I've confirmed the original issue reported here is still occurring, as it relates to React specifically or perhaps lazy loading in general, so I'm going to leave this one open. In particular with this issue you'll get warnings in the console but everything will actually work as expected.

If anyone else reading this experiences a similar issue but things don't work as expected (in other words, you get these console warnings AND blocks/toolboxes actually appear broken) please open a new issue as that would not be related to this one. Thank you!

[frck006]

Hi,
I use @sveltejs/kit, vite 3.1.8 and with Blockly V9.0.1, the problem is always here:

[DaveWelling]

This creates a lot of garbage in our unit tests logs.
I know this workaround is ugly, but If you get as desperate as I was to get rid of this you can load your Blockly dependency like so:

/* eslint-disable */
// ******************************************************************************
// See issue https://github.com/google/blockly/issues/4369
// Blockly will not allow you to avoid printing out a bunch of useless
// localization warnings for messages we don't use.
// This clogs up unit testing logs, etc.
// The versions for both log and warn are because they keep changing which ones they are
// using across builds.
const tempConsoleLog = console.log;
const tempConsoleWarn = console.warn;
let Blockly;
try {
    console.log = message => {
        if (message.startsWith('WARNING: No message string for %{')) return;
        else tempConsoleLog(message);
    };
    console.warn = message => {
        if (message.startsWith('No message string for %{')) return;
        else tempConsoleWarn(message);
    };
    Blockly = require('blockly');
} finally {
    console.log = tempConsoleLog;
    console.warn = tempConsoleWarn;
}
// ******************************************************************************
/* eslint-enable */

I found we only needed to do this once in our entry point.

[semiaddict]

@maribethb,

... as it relates to React specifically or perhaps lazy loading in general...

This seems to be a general issue with lazy loading, as I am experiencing the same thing when lazy loading Blockly in a Vue 3 app.

[doctorpangloss]

Can this be resolved for real? I appreciate the purpose of these messages for developers, but it doesn't make sense to have them for end users.

[stasberkov]

M.b. introduce a flag do not show such errors when compile for prod mode?

[rachel-fenichel]

@cpcallen this now happens in the playground, after your recent change to bootstrapping/loading. Did you expect that?