Why do I get the error "TPA handler message caller does not belong to any page "?

Ask the community
,
1

When I click on some links on my home page I get the error “TPA handler message caller does not belong to any page”. I tried the dashboard site monitoring. But it does not show up in site monitoring.

svwoodturners.com is the site.

Here is what it looks like:

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

TPA handler message caller does not belong to any page

Object { type: “appStateChanged”, callId: undefined, compId: “comp-kbh2mog8” } tpaMessageContextPicker.ts:91:15 handleEvent tpaMessageContextPicker.ts:91

i (index):131

i (index):131

i (index):131

i (index):131

handleEvent tpaCommons.799c7531.chunk.min.js:1

78092 (index):167

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

TPA handler message caller does not belong to any page

Object { type: “appStateChanged”, callId: undefined, compId: “comp-kbh2mog8” } tpaMessageContextPicker.ts:91:15

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

Loading the code for the site. To debug this code, open masterPage.js in Developer Tools. workerLogger.js:103:17

TPA handler message caller does not belong to any page

Object { type: “appStateChanged”, callId: undefined, compId: “comp-kbh2mog8” }
tpaMessageContextPicker.ts:91:15
handleEvent tpaMessageContextPicker.ts:91

i (index):131

i (index):131

i (index):131

i (index):131

handleEvent tpaCommons.799c7531.chunk.min.js:1

78092

2

Is this problem still occurring? I don’t see this message appearing for any of the links that I’ve tried. Does it happen on any specific links?

3

This happens only on the home page. When I am on the home page and click on one of the tiles on that page. Each of those tiles is just an image that links to a page. Nothing fancy there. I know it is not coming from the rendering of the destination page since a refresh of that page does not show that error.

4

Which tiles exactly does this problem occur? I just don’t see those error messages about the TPA.

5

For example click on “Member Galleries” from the home page.

1926×1086 511 KB

In the above img, I clicked on “Member Galleries” which produced the error. Then I went back to the home page before capturing the screen shot.

6

Hmmm, no error:

3070×1202 494 KB

7

It’s only on Mozilla Firefox

8

@jonatandor35 aha - I was gonna ask on what browser(s)…

So, then does it fail (on FF)? Or does it only give a scary error message? And what about other browsers?

9

@yisrael-wix It does not fail on FF. It just gives the message. So I am not too concerned about it. The error message does not show up in chrome or edge. I think I will ignore this error and concentrate on the other 2 issues, namely the editor performance and the one about the CurrentIndexChanged as described in
https://www.wix.com/velo/forum/coding-with-velo/dataset-refresh-gives-an-error-but-no-way-to-catch-it?appSectionParams=%7B%22origin%22%3A%22member_posts_page%22%7D

10

@siliconvalleywoodtur You may not be concerned about the “TPA messages” but I certainly am, and I imagine the dev team will be too. I am going to send this on to the devs for evaluation. It might be nothing, but it might be something. At least it works for you, and that’s what’s of immediate importance.

As far as the editor performance, I would suggest trying your best to isolate the CurrentIndexChanged to one dataset and its connected Repeater. It will be much easier to fix if you only see it in one place.

11

on my web page i do have this issue too. and it seems suddenly appears.

12

J’ai également ce problème sur mon site, il est très souvent impossible de cliquer autre part après avoir ajouter un article au panier