[Optimizely App] variation container allows incorrect variant type to be selected on first render about apps HOT 7 CLOSED

I have identified the cause of the issue.

The API request space.getEntries({ links_to_entry: ids.entry, skip: 0, limit: 1000 }) sometimes returns an empty items array.

I have reproduced the error programatically and this bug manifests because the contentful API is eventually consistent. Adding a delay between linking the VariationContainer to the HomePage and fetching the entries that link to the HomePage mitigates the bug.

from apps.

@juancarlosjr97 Thanks for reaching out! This ticket has not been prioritized, but I will provide an update when we are working on it.

from apps.

Hi @LucasAmos! Thank you for raising this issue. As communicated through our support process, we have captured this issue in our backlog and will prioritize it as soon as possible.

from apps.

Just another quick update @LucasAmos. I am going to close this issue and we will continue to communicate updates to you about this bug through our internal support process. Thank you!

from apps.

Any update on this ticket? As this has been closed makes following it up is practically impossible.

from apps.

@whitelisab... As @LucasAmos mentioned, the issue is the line

The reason, we think, is happening is because when the entry is created, it opens immediately the drawer and does the fetch of the L86, but as Contentful has just created the entry, the relationship does not exist yet, and if the patch of the parent entry with the newly created entry happens before the fetch data of L86 the array returns correct data, but if it happens after, it returns an empty array as the linked relationship does not exist yet.

Long story short, it requires an await for however long contentful takes to save an empty when a change happens on the UI and does the path.

from apps.

I have raised an MR to fix the bug - #4621 @whitelisab.

Please, if you could review it and merge it as we need this fix.

from apps.