feat(network-activity-plugin): support timeout and in-progress network activity event#147
Merged
V3RON merged 4 commits intocallstackincubator:mainfrom Nov 26, 2025
Conversation
|
@dprevost-LMI is attempting to deploy a commit to the Callstack Team on Vercel. A member of the Team first needs to authorize it. |
6 tasks
V3RON
approved these changes
Nov 19, 2025
Contributor
Author
|
Would you like me to resolve the issues below so the PR can be merged into develop?
Never mind just saw the below:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adding support for
timeoutwhen a request fails, and thein-progressthat displays % progress in the status columnRelated Issue
See #149
Context
After code inspection, I noticed a missing handling of the timeout case, and I was able to implement the in-progress feature quickly, so I have done so.
Testing
For the timeout, no suitable calls were found to reproduce it! If needed, I can take more time!
Tested as seen below with the emulator downgrading speed.
Screen.Recording.2025-11-16.at.10.33.54.AM.mov
The large file implemented for the above tests
