Cannot access API key page

(Paul White) #1

Hi I am having a problem accessing the API Key page. When I access it, it loads, the disappears. Very strange!
I am using Firefox 60.3.0esr (64-bit) on Debian Stretch, Linux 4.9.0.

To better explain the problem, I recorded what happens

Any idea what is going on?


(Takuya Matsuyama) #2

Hi Paul,

Thank you for reporting.
That’s weird. I checked it works correctly on Firefox, macOS.
I couldn’t open your link (connection failed) so could you check it?

(Paul White) #3

Sorry, the link should work now.

(Takuya Matsuyama) #4

Thanks. I viewed your video. Yeah, that’s so strange. Seems like the entire web app or React itself crashed.
I would like to know:

  1. Is there any error in console?
  2. Does it only occur at API keys page?

(Paul White) #5

Hi Takuya,

Output from the console:-

[bugsnag] Loaded! app.js:57:261468

The resource at “” was blocked because tracking protection is enabled.[Learn More] api-keys

Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src”). Source: ;!function(){var t,e,n,o=0,u=function(t,… controller-cdfa7859b4d3c7a31260f862393869cc.html:1

Invariant Violation: Minified React error #185; visit for the full message or use the non-minified dev environment for full errors and additional helpful warnings. Stack trace: o/<@ o@ ja@ enqueueSetState@ g.prototype.setState@ b/</o</o.prototype.onStateChange@ notify@ m</e.prototype.notifyNestedSubs@ b/</o</o.prototype.onStateChange@ notify@ m</e.prototype.notifyNestedSubs@ b/</o</o.prototype.onStateChange@ _@ o/</</<@ L/</</<@ c/<@ value@ value@ value@ Li@ $i@ Qi@ Sa@ Ya@ co@ uo@ ho@ He@ Sn@


This only happens on the api keys page. All other pages are OK.
I tried disabling tracking prevention for, but that had no effect.

(Takuya Matsuyama) #6

Thank you, Paul.
I’ll try to reproduce it!

(Paul White) #7

Could it be a clash with a plugin?

I have the following installed and enabled:-

Just a thought.

(Takuya Matsuyama) #8

Possibly. To clarify, could you try it on other browsers?

(Paul White) #9

I tried it in Chrome Version 70.0.3538.110 (Official Build) (64-bit) with the same result. No extensions, and clean install as I don’t use it.

(Takuya Matsuyama) #10

Thank you for the information.
I’m struggling to reproduce it.
I checked your account but it seems no problem.
Just in case, I updated React version so perhaps it might fix the problem.
I’ll deploy a dev build to another domain so that we can see the React error report.
Please wait for a while.
Sorry for the inconvenience!

(Takuya Matsuyama) #11

I tried to reproduce it on Debian but couldn’t:

  • Debian 9 (stretch)
  • Linux 4.9.0-8-amd64
  • Firefox 60.3.0esr

As we talked through email, the problem also occurs with the demo account. So your account doesn’t cause it.
I guess it’s your environment problem and please try it on other machine.