Cannot access API key page

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 https://cloud.vascowhite.co.uk/s/DYCeBTF96tj2faT

Any idea what is going on?

Cheers

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?

Sorry, the link should work now.

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?

Hi Takuya,

Output from the console:-

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

The resource at “https://api.mixpanel.com/decide/?verbose=1&version=1&lib=web&token=058c4ca480354f1f0821217c79e7f0a7&ip=1&_=1543570017357” 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 Minified React error #185 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings. Stack trace: o/<@Inkdrop - Organizing Markdown notes made simple o@Inkdrop - Organizing Markdown notes made simple ja@Inkdrop - Organizing Markdown notes made simple enqueueSetState@Inkdrop - Organizing Markdown notes made simple g.prototype.setState@Inkdrop - Organizing Markdown notes made simple b/</o</o.prototype.onStateChange@Inkdrop - Organizing Markdown notes made simple notify@Inkdrop - Organizing Markdown notes made simple m</e.prototype.notifyNestedSubs@Inkdrop - Organizing Markdown notes made simple b/</o</o.prototype.onStateChange@Inkdrop - Organizing Markdown notes made simple notify@Inkdrop - Organizing Markdown notes made simple m</e.prototype.notifyNestedSubs@Inkdrop - Organizing Markdown notes made simple b/</o</o.prototype.onStateChange@Inkdrop - Organizing Markdown notes made simple _@Inkdrop - Organizing Markdown notes made simple o/</</<@Inkdrop - Organizing Markdown notes made simple L/</</<@Inkdrop - Organizing Markdown notes made simple c/<@Inkdrop - Organizing Markdown notes made simple value@Inkdrop - Organizing Markdown notes made simple value@Inkdrop - Organizing Markdown notes made simple value@Inkdrop - Organizing Markdown notes made simple Li@Inkdrop - Organizing Markdown notes made simple $i@Inkdrop - Organizing Markdown notes made simple Qi@Inkdrop - Organizing Markdown notes made simple Sa@Inkdrop - Organizing Markdown notes made simple Ya@Inkdrop - Organizing Markdown notes made simple co@Inkdrop - Organizing Markdown notes made simple uo@Inkdrop - Organizing Markdown notes made simple ho@Inkdrop - Organizing Markdown notes made simple He@Inkdrop - Organizing Markdown notes made simple Sn@Inkdrop - Organizing Markdown notes made simple

app.js:57:266772

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

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

Could it be a clash with a plugin?

I have the following installed and enabled:-

Just a thought.

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

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.

1 Like

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!

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.