We have updated Flexmonster Software License Agreement, effective as of September 30, 2024. Learn more about what’s changed.

"Something went wrong" popup

Closed
shahar ben shimon asked on February 9, 2023

Hello,
We are using the latest vue-flexmonster (2.9.44)
We randomly get the "something wen wrong" popup, usually a few seconds after the Pivot Table component initial load (before loading any data or report).

Something went wrong.
To fix the issue please try the following:
1. Check if the componentFolder parameter is defined correctly.
2. Check if the path to the css file is valid.
3. Check if DevTools (press F12) has an exception.
4. Ask the support team for help

Despite the error, everything seems to work fine.
This is the error and the full stack trace we see in the DevTools console:

Uncaught TypeError: Cannot read properties of null (reading 'element')
at new k (flexmonster.full.js?312d:100:162)
at h.Ie (flexmonster.full.js?312d:1606:76)
at eval (flexmonster.full.js?312d:1594:270)
k @ flexmonster.full.js?312d:100
Ie @ flexmonster.full.js?312d:1606
eval @ flexmonster.full.js?312d:1594
requestAnimationFrame (async)
requestAnimationFrame @ flexmonster.full.js?312d:151
u.io.load.dO @ flexmonster.full.js?312d:1592
load @ flexmonster.full.js?312d:87
h @ flexmonster.full.js?312d:1592
k @ flexmonster.full.js?312d:2425
PivotApi @ flexmonster.full.js?312d:2442
eval @ flexmonster.full.js?312d:2452
mounted @ index.esm.js?e538:61
invokeWithErrorHandling @ vue.esm.js?a026:1872
callHook @ vue.esm.js?a026:4244
insert @ vue.esm.js?a026:3167
invokeInsertHook @ vue.esm.js?a026:6401
patch @ vue.esm.js?a026:6620
Vue._update @ vue.esm.js?a026:3972
updateComponent @ vue.esm.js?a026:4090
get @ vue.esm.js?a026:4504
run @ vue.esm.js?a026:4579
flushSchedulerQueue @ vue.esm.js?a026:4335
eval @ vue.esm.js?a026:1998
flushCallbacks @ vue.esm.js?a026:1924
Promise.then (async)
timerFunc @ vue.esm.js?a026:1951
nextTick @ vue.esm.js?a026:2008
queueWatcher @ vue.esm.js?a026:4427
update @ vue.esm.js?a026:4569
notify @ vue.esm.js?a026:739
reactiveSetter @ vue.esm.js?a026:1064
eval @ vue-router.esm.js?8c4f:3003
eval @ vue-router.esm.js?8c4f:3002
updateRoute @ vue-router.esm.js?8c4f:2414
eval @ vue-router.esm.js?8c4f:2263
eval @ vue-router.esm.js?8c4f:2402
step @ vue-router.esm.js?8c4f:2001
step @ vue-router.esm.js?8c4f:2008
runQueue @ vue-router.esm.js?8c4f:2012
eval @ vue-router.esm.js?8c4f:2397
step @ vue-router.esm.js?8c4f:2001
eval @ vue-router.esm.js?8c4f:2005
eval @ vue-router.esm.js?8c4f:2384
eval @ vue-router.esm.js?8c4f:2162
iterator @ vue-router.esm.js?8c4f:2362
step @ vue-router.esm.js?8c4f:2004
step @ vue-router.esm.js?8c4f:2008
step @ vue-router.esm.js?8c4f:2008
runQueue @ vue-router.esm.js?8c4f:2012
confirmTransition @ vue-router.esm.js?8c4f:2392
transitionTo @ vue-router.esm.js?8c4f:2260
push @ vue-router.esm.js?8c4f:2606
push @ vue-router.esm.js?8c4f:3037
handler @ vue-router.esm.js?8c4f:1139
invokeWithErrorHandling @ vue.esm.js?a026:1872
invoker @ vue.esm.js?a026:2197
original._wrapper @ vue.esm.js?a026:7609

Could you please help?
 
Thanks,
Shahar

2 answers

Public
shahar ben shimon February 9, 2023

We found out that the error showed up starting from the second Pivot component rendering.
We were able to fix it by un-mounting the Pivot component when switching to another page in our app, and mounting it back when switching back to the page where the Pivot component is rendered.

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster February 9, 2023

Hello, Shahar,

We are glad to hear that you fixed the issue.

As always, feel free to reach out in case other questions arise.

Kind regards,
Nadia 

This question is now closed