Skip to content

[Fix] Flipper Warning #285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 2, 2024
Merged

[Fix] Flipper Warning #285

merged 1 commit into from
Sep 2, 2024

Conversation

stevensJourney
Copy link
Collaborator

@stevensJourney stevensJourney commented Sep 2, 2024

Overview

A debug log is printed if using Android and the HTTP network request failed to resolve in 30 seconds. This is usually due to the Flipper debug tool causing HTTP stream requests to never resolve (or reject). The timeout for this log was cleared if the HTTP request resolves.

The Flipper warning log would still show after the timeout expired even if the network request rejected. This updates the logic to clear the timeout if the HTTP request rejects or resolves.

Testing

Verified that the timeout is cleared if the request resolves or rejects. HTTP streaming also functions normally.

Copy link

changeset-bot bot commented Sep 2, 2024

🦋 Changeset detected

Latest commit: 586183c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@powersync/react-native Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@stevensJourney stevensJourney marked this pull request as ready for review September 2, 2024 14:15
@stevensJourney stevensJourney merged commit 892e172 into main Sep 2, 2024
4 checks passed
@stevensJourney stevensJourney deleted the fix/android-http-warning branch September 2, 2024 15:09
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.

3 participants