Metabase-i18n-debug in embedded dashboard in React in Brave

I'm embedding a Metabase dashboard in a React application. The embedded dashboard works in Chrome, but when I access the local development web server via Brave I get this error in the console (and Metabase doesn't render the embedded dashboard):

Uncaught TypeError: Cannot read property 'metabase-i18n-debug' of null
    at Object.58807 (i18n-debug.js:57)
    at o (bootstrap:19)
    at Object.34470 (alert.js:186)
    at o (bootstrap:19)
    at ga-metadata.js?27af:5
    at Function.o.O (chunk loaded:25)
    at ga-metadata.js?27af:5
    at n (jsonp chunk loading:73)
    at app-embed.bundle.js?ff357d02a1e90457282d:2

But, when I access to the production version (deployed in my server) of the same page via Brave all works well!

Any suggestions to work in locale with Brave?

Here my diagnostic info

  "browser-info": {
    "language": "it-IT",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "",
    "java.version": "",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "",
    "": "Linux",
    "os.version": "5.10.127+",
    "user.language": "en",
    "user.timezone": "UTC"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "13.7"
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.4.1"
    "run-mode": "prod",
    "version": {
      "date": "2022-09-02",
      "tag": "v1.44.3",
      "branch": "release-x.44.x",
      "hash": "7d50282"
    "settings": {
      "report-timezone": "Europe/Rome"

Hi @alberto.manfrinati
I doubt that the error is the only one. I have a feeling that there's other errors.
Usually modern browsers really don't like mixed protocols (http and https) nor local development addresses (localhost etc), and some browser functionality is only available via https.

1 Like