Community X.

Connect with other creators, share ideas, give feedback and get the latest product updates.

Nov 1, 2020
Edited: Nov 2, 2020

Error on Dynamic Page Navigation

Hello, I am having some issues with dynamic pages.

I created a dynamic page from a Themes dataset that contains a column with a reference to the store/Collections dataset.


I have 3 datasets inside the dynamic page,

- Themes dataset that is added by default: displays 1 item based on the url.

- Stores/Collections dataset: display 1 item - filter: name = Themes dataset title column.

- Store/Products dataset: display 12 items - filter: includes current item from Stores/Collections dataset.


If I am on the home page and click the item that navigates to the dynamic page, it works just fine, I can see the Products in a repeater for the Theme and the Collection referenced.


However, If I then go back to the home page and press the gallery item again, the dynamic page opens blank, no headers or footers or anything.. and the error below shows up in the console.

This page is the only place where I have custom code, but even when removing the code I get the same error.


  • It appears that in preview mode the problem does not happen.

  • I tried removing the datasets and code from the Theme dynamic pages and the issue still happens.

  • Navigating through the links in the pages causes the issue. If I navigate by manually typing the URL in the browser the issue does not happen.

  • I tried creating new buttons with links to test without success.

  • I tried duplicating the Site and the issue still remains on the new site.

  • Sometimes I get HTTP 429 too many requests, but the issue above happens even when I don't get the HTTP 429.



I'm honestly clueless and I'm starting to believe this a bug on Edtitorx.


Can anyone help me, please?


Uncaught (in promise) TypeError: Cannot read property 'resolvePublicApiGetter' of null
    at Object.registerPublicApiGetter (tpa.f085e87a.chunk.min.js:1)
    at Object.<anonymous> (platform.3e14dcc3.chunk.min.js:1)
    at minnie:105
    at Object.next (minnie:105)
    at c (minnie:105)
deserialize @ comlink.ts:265
w @ comlink.ts:519
Promise.then (async)
apply @ comlink.ts:442
invokeSdkHandler @ clientWorker.ts:33
(anonymous) @ index.ts:42
registerAppsPublicApis @ appsPublicAPIs.ts:18
(anonymous) @ applications.ts:200
(anonymous) @ tslib.es6.js:100
(anonymous) @ tslib.es6.js:81
a @ tslib.es6.js:71
Promise.then (async)
u @ tslib.es6.js:73
a @ tslib.es6.js:71
Promise.then (async)
u @ tslib.es6.js:73
(anonymous) @ tslib.es6.js:74
s @ tslib.es6.js:70
startApplications @ clientWorker.8ada89de.bundle.min.js:1
(anonymous) @ platformLoggerFactory.ts:105
(anonymous) @ tslib.es6.js:100
(anonymous) @ tslib.es6.js:81
(anonymous) @ tslib.es6.js:74
s @ tslib.es6.js:70
runAsyncAndReport @ platformLoggerFactory.ts:102
(anonymous) @ index.ts:181
(anonymous) @ tslib.es6.js:100
(anonymous) @ tslib.es6.js:81
a @ tslib.es6.js:71
Promise.then (async)
u @ tslib.es6.js:73
(anonymous) @ tslib.es6.js:74
s @ tslib.es6.js:70
js @ clientWorker.8ada89de.bundle.min.js:1
(anonymous) @ worker.ts:71
(anonymous) @ tslib.es6.js:100
(anonymous) @ tslib.es6.js:81
(anonymous) @ tslib.es6.js:74
s @ tslib.es6.js:70
Ms @ clientWorker.8ada89de.bundle.min.js:1
(anonymous) @ clientWorker.ts:70
(anonymous) @ tslib.es6.js:100
(anonymous) @ tslib.es6.js:81
(anonymous) @ tslib.es6.js:74
s @ tslib.es6.js:70
(anonymous) @ clientWorker.ts:16
n @ comlink.ts:312
2react-dom.production.min.js:209 Error: Component is missing from structure. displayedId: lj7gg. id: lj7gg
    at P (StructureComponent.tsx:79)
    at $i (react-dom.production.min.js:153)
    at go (react-dom.production.min.js:261)
    at cu (react-dom.production.min.js:246)
    at ou (react-dom.production.min.js:246)
    at Zo (react-dom.production.min.js:239)
    at react-dom.production.min.js:123
    at t.unstable_runWithPriority (scheduler.production.min.js:19)
    at Wl (react-dom.production.min.js:122)
    at Kl (react-dom.production.min.js:123)

Nov 3, 2020

No one? I'm suspecting my issue is the HTTP 429 too many requests error even though I don't see it in the dev console every time. Maybe Editorx backend caches the response and doesn't even try to call the endpoint again, and that is why I don't see 429 every time? If 429 is indeed the issue, the time limitation seems to be too low. I can literally induce the error in two tries and I can definitely see this affecting real costumers.

Editor X

Design your boldest creations.