Skip to content

Fix getRectForRef - current not set error#193

Open
evelant wants to merge 1 commit into
SteffeyDev:masterfrom
evelant:fix/getRectForRef-current-not-set
Open

Fix getRectForRef - current not set error#193
evelant wants to merge 1 commit into
SteffeyDev:masterfrom
evelant:fix/getRectForRef-current-not-set

Conversation

@evelant

@evelant evelant commented May 8, 2025

Copy link
Copy Markdown

fixes #153 error filing people's logs. It is valid when current is not set because of the timeout used, the component may have unmounted.

…ing logs. It is valid when current is not set because of the timeout used, the component may have unmounted.
@AdamGerthel

AdamGerthel commented May 9, 2025

Copy link
Copy Markdown
Collaborator

I'm seeing a lot of unrelated changes. Could you clean up the PR to only include the relevant changes?

It looks like you're catching the error and then returning an incorrect Rect value. Could you explain how this solves the problem?

Isn't the solution to this whole problem that the component needs to clear the timeout when it unmounts? In other words, the timeout needs to be stored in a React.ref which is then called through clearTimeout in a useEffect return function

@freeboub

Copy link
Copy Markdown

Any update on this PR, I am also affected by this issue ...

@jakedeg

jakedeg commented Jan 16, 2026

Copy link
Copy Markdown

Just bumping this. It's affecting us too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error: getRectForRef - current is not set (Unhandled Promise Rejection) iOS

4 participants