Re-render controls when lastError changes

[leszko]

Description

This PR fixes the issue that the player may not re-render when an error happens. Here's a scenario we encounter in Daydream App:

1. Effect Store is created with the default params
2. Error happens, the errorCount is increased to the value of 2, the player is re-rendered as expected
3. Parent component is re-rendered, which causes the store to re-create, errorCount is again 1
4. Error happens, the errorCount is increased to the value of 2, the player is not re-rendered, because errorCount has not changed (it is again 2); visually, a users sees a grey screen instead of the stream playback.

This PR fixes this issue, because by having lastError timestamp in the equality function, we will always re-render the player if any error happens.

Side note re point 3: I'm not 100% sure why we re-render the parent component and why it causes the store to be recreated. I see we're re-rendering all the components every 1s, and that causes (sometimes) the store recreation. @junhyr @gioelecerati you may have some ideas here.

Additional Information

• I read the contributing docs (if this is your first contribution)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
coinbase-lvpr-tv	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am
lvpr-tv	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am
ui-kit-docs-embed	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am
ui-kit-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am
ui-kit-next-pages	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am
ui-kit-with-pubnub	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:09am

[leszko]

There are some CI failures but they are unrelated to this PR