umami: after update to 1.25 a client-side exception has occurred

after updating to v1.25.0 I cant accsess the /dashboard or any site stats page /website/1/blog or /settings/profile

getting the error:

Application error: a client-side exception has occurred (see the browser console for more information).

yarn: 1.22.15 npm: 7.24.2 node: v14.18.0

on server: Ubuntu 20.04.3 LTS

the console output:

framework-91d7f78b5b4003c8.js:1 SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at m (_app-55a9810cbf8ca279.js:1:409752)
    at f (752-fdafd5228e3660dc.js:1:16156)
    at Nn (803-a5a0aa08ee49a343.js:1:38783)
    at ro (framework-91d7f78b5b4003c8.js:1:59430)
    at Hu (framework-91d7f78b5b4003c8.js:1:111888)
    at Pi (framework-91d7f78b5b4003c8.js:1:99062)
    at xi (framework-91d7f78b5b4003c8.js:1:98990)
    at _i (framework-91d7f78b5b4003c8.js:1:98853)
    at vi (framework-91d7f78b5b4003c8.js:1:95819)
uu @ framework-91d7f78b5b4003c8.js:1
a.componentDidCatch.n.callback @ framework-91d7f78b5b4003c8.js:1
fa @ framework-91d7f78b5b4003c8.js:1
hu @ framework-91d7f78b5b4003c8.js:1
Li @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ti @ framework-91d7f78b5b4003c8.js:1
vi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ql @ framework-91d7f78b5b4003c8.js:1
Hl @ framework-91d7f78b5b4003c8.js:1
fi @ framework-91d7f78b5b4003c8.js:1
No @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
s @ main-6dbd9d9da1881058.js:1
(anonymous) @ main-6dbd9d9da1881058.js:1
S.forEach.e.<computed> @ main-6dbd9d9da1881058.js:1
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
h @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
Fi @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Oi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
I @ framework-91d7f78b5b4003c8.js:1
w.port1.onmessage @ framework-91d7f78b5b4003c8.js:1
main-6dbd9d9da1881058.js:1 SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at m (_app-55a9810cbf8ca279.js:1:409752)
    at f (752-fdafd5228e3660dc.js:1:16156)
    at Nn (803-a5a0aa08ee49a343.js:1:38783)
    at ro (framework-91d7f78b5b4003c8.js:1:59430)
    at Hu (framework-91d7f78b5b4003c8.js:1:111888)
    at Pi (framework-91d7f78b5b4003c8.js:1:99062)
    at xi (framework-91d7f78b5b4003c8.js:1:98990)
    at _i (framework-91d7f78b5b4003c8.js:1:98853)
    at vi (framework-91d7f78b5b4003c8.js:1:95819)
ye @ main-6dbd9d9da1881058.js:1
fn @ main-6dbd9d9da1881058.js:1
value @ main-6dbd9d9da1881058.js:1
a.componentDidCatch.n.callback @ framework-91d7f78b5b4003c8.js:1
fa @ framework-91d7f78b5b4003c8.js:1
hu @ framework-91d7f78b5b4003c8.js:1
Li @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ti @ framework-91d7f78b5b4003c8.js:1
vi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ql @ framework-91d7f78b5b4003c8.js:1
Hl @ framework-91d7f78b5b4003c8.js:1
fi @ framework-91d7f78b5b4003c8.js:1
No @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
s @ main-6dbd9d9da1881058.js:1
(anonymous) @ main-6dbd9d9da1881058.js:1
S.forEach.e.<computed> @ main-6dbd9d9da1881058.js:1
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
h @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
Fi @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Oi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
I @ framework-91d7f78b5b4003c8.js:1
w.port1.onmessage @ framework-91d7f78b5b4003c8.js:1
main-6dbd9d9da1881058.js:1 A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred
ye @ main-6dbd9d9da1881058.js:1
fn @ main-6dbd9d9da1881058.js:1
value @ main-6dbd9d9da1881058.js:1
a.componentDidCatch.n.callback @ framework-91d7f78b5b4003c8.js:1
fa @ framework-91d7f78b5b4003c8.js:1
hu @ framework-91d7f78b5b4003c8.js:1
Li @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ti @ framework-91d7f78b5b4003c8.js:1
vi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Ql @ framework-91d7f78b5b4003c8.js:1
Hl @ framework-91d7f78b5b4003c8.js:1
fi @ framework-91d7f78b5b4003c8.js:1
No @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
s @ main-6dbd9d9da1881058.js:1
(anonymous) @ main-6dbd9d9da1881058.js:1
S.forEach.e.<computed> @ main-6dbd9d9da1881058.js:1
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
Promise.then (async)
u @ 803-a5a0aa08ee49a343.js:1
l @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
h @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
(anonymous) @ 803-a5a0aa08ee49a343.js:1
Fi @ framework-91d7f78b5b4003c8.js:1
t.unstable_runWithPriority @ framework-91d7f78b5b4003c8.js:1
$l @ framework-91d7f78b5b4003c8.js:1
Oi @ framework-91d7f78b5b4003c8.js:1
(anonymous) @ framework-91d7f78b5b4003c8.js:1
I @ framework-91d7f78b5b4003c8.js:1
w.port1.onmessage @ framework-91d7f78b5b4003c8.js:1

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (8 by maintainers)

Commits related to this issue

Fix custom date range display. Closes #923, #921 — committed to umami-software/umami by mikecao 2 years ago
Fix custom date range display. Closes #923, #921 — committed to withflint/umami by mikecao 2 years ago

Most upvoted comments

Facing the same issue, When the All Time value is set from the Settings page, then it crashed because the value is set as undefined

ShubhamVerma1811 on Jan 19, 2022

Certainly so… Changing ‘Default date range’ in Profile settings results in ‘umami.date-range:undefined’

t3brightside on Feb 17, 2022

Fixed in v1.26.0.

mikecao on Feb 17, 2022

Can you trying deleting all your localStorage values?

mikecao on Jan 18, 2022