Getting a "We're sorry, but something went wrong with the Mastodon app" when refreshing it on desktop

[jenniedo]

Steps to reproduce the problem

1. Refresh mstdn.ca in a Firefox window on a Mac laptop

...

Expected behaviour

It should have shown me my normal display on mstdn.ca

Actual behaviour

I got the error "We're sorry, but something went wrong with the Mastodon app."

Detailed description

Here's the debug information:
Stack trace

TypeError: this.props.account is undefined
render@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:1565180
Uo@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:287321
zo@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:287116
ws@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:322614
mu@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:314090
_u@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:314013
su@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:311043
Qi/<@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:262791
t.unstable_runWithPriority@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:337673
$i@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:262500
Qi@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:262738
Yi@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:262671
au@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:307828
enqueueSetState@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:266456
y.prototype.setState@https://mstdn.ca/packs/js/common-34fd9debdd2c40d07f79.chunk.js:2:212395
681/c/this.load/<@https://mstdn.ca/packs/js/333-6efdf03c5080b3eedbff.chunk.js:2:151688

Mapped stack trace

TypeError: this.props.account is undefined
intl.formatMessage (webpack:///app/javascript/home/mastodon/live/app/javascript/mastodon/components/status_action_bar.jsx:349:48)
gi (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:3574:7)
Lg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:3568:1589)
ig (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:5476:6)
Bg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:5025:12)
Ag (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:5021:)
yj (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:4806:12)
gg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:2318:4)
unstable_runWithPriority (webpack:///node_modules/scheduler/cjs/scheduler.production.min.js:238:)
bg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:2290:9)
eg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:2311:49)
dg (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:2308:12)
Ig (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:4647:11)
enqueueSetState (webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:2564:19)
F (webpack:///node_modules/react/cjs/react.production.min.js:45:12)
this.setState (webpack:///app/javascript/home/mastodon/live/app/javascript/flavours/glitch/features/ui/components/bundle.jsx:80:13)

React component stack

    in F
    in Connect(F)
    in InjectIntl(Connect(F))
    in div
    in div
    in div
    in G
    in InjectIntl(G)
    in Connect(InjectIntl(G))
    in c
    in Connect(c)
    in div
    in ht
    in Connect(ht)
    in Connect(ht)
    in qt
    in div
    in div
    in t
    in t
    in Ft
    in t
    in withRouter(Ft)
    in InjectIntl(withRouter(Ft))
    in Connect(InjectIntl(withRouter(Ft)))
    in t
    in t
    in t
    in withRouter(t)
    in t
    in t
    in zt
    in c
    in IntlProvider
    in en

Specifications

Mac OS Mojave running Firefox 11.0.1

[ClearlyClaire]

I am sorry, I'm unable to reproduce the issue.

Can you reliably reproduce it? Does it happen on any Mastodon page or on some page in particular? Are you using the single-column layout or the advanced view?

[yllekz]

Getting this too on infosec.exchange but when selecting "filter this post" on a post in the local timeline.

[ClearlyClaire]

@yllekz that's a separate issue, #2186