`init` doesn't work when called too late about ui-extensions-sdk HOT 7 CLOSED

Hey @r00dY - if this still an issue for you, can you provide a minimal setup for replicating the issues? I believe that the sdk should be storing all messages before init is called, so they can be handled at the appropriate time.

from ui-extensions-sdk.

Closing because of inactivity. Feel free to reopen if you are still running into issues.

from ui-extensions-sdk.

@Jwhiles what if connect message is sent before your SDK is loaded? I must lazy load your SDK because of #1046 and message comes before the load.

from ui-extensions-sdk.

@r00dY I think

@Jwhiles what if connect message is sent before your SDK is loaded? I must lazy load your SDK because of #1046 and message comes before the load.

@r00dY I think I'm experiencing this. It's VERY frustrating - and I can't quite pin down when/how to avoid missing this call so my extension only works 1/4 of the time...did you find any solutions?

from ui-extensions-sdk.

We are aware of the issues and are currently working on a solution. We hope to release an update of the App SDK at some point next month but cannot provide an ETA just yet.

I don't think there is a workaround for this problem. Currently, the App SDK must be included in the first chunk loaded by the app. If the SDK is loaded later (e.g. via dynamic loading, lazy loading), things become flaky.

(Reopening this issue to communicate the status of our work.)

from ui-extensions-sdk.

We released an alpha version that hopefully resolves your issues: 4.10.0-alpha.1. Would be great to hear from you folks whether you are still running into problems with that update.

You can install the alpha by running npm install @contentful/[email protected]

from ui-extensions-sdk.

The change is now available in 4.11.0.

from ui-extensions-sdk.