Skip to content
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

[Bug]: HTTP-Plugin on iOS: load events not fired #7416

Closed
2 of 3 tasks
wif70068 opened this issue Apr 19, 2024 · 3 comments
Closed
2 of 3 tasks

[Bug]: HTTP-Plugin on iOS: load events not fired #7416

wif70068 opened this issue Apr 19, 2024 · 3 comments
Labels
needs reproduction needs reproducible example to illustrate the issue

Comments

@wif70068
Copy link

wif70068 commented Apr 19, 2024

Capacitor Version

Latest Dependencies:

@capacitor/cli: 6.0.0
@capacitor/core: 6.0.0
@capacitor/android: 6.0.0
@capacitor/ios: 6.0.0

Installed Dependencies:

@capacitor/cli: 5.7.4
@capacitor/android: 5.7.4
@capacitor/ios: 5.7.4
@capacitor/core: 5.7.4

Other API Details

npm: 10.5.0
node: v21.7.1
pod: 1.15.2

Platforms Affected

  • iOS
  • Android
  • Web

Current Behavior

Upon launching the app, we've observed intermittent occurrences where an XHR request, configured with CapacitorHttp: { enabled: true }, fails to trigger a response. None of the expected events such as load, loadend, abort, progress, or error are triggered, leaving the xhr request indefinitely in readystate=2. External network issues have been ruled out, and the iOS console confirms successful completion of the request.

Reproducing this issue is challenging, but similar behavior was encountered when setting JavaScript debug breakpoints after the request initiation but before its completion. Upon resuming execution, the expected events failed to trigger.

Further investigation revealed that certain lines (788, 828, or 851) within native-bridge.ts (https://github.com/ionic-team/capacitor/blob/main/core/native-bridge.ts) are never reached, indicating potential loss of the native response.

Expected Behavior

The request finishes successfully.

Project Reproduction

.

Additional Information

No response

@wif70068
Copy link
Author

wif70068 commented Apr 23, 2024

our monitoring just witnessed the first case on android. Can't reproduce with setting JavaScript debug breakpoints on Android.

@jcesarmobile jcesarmobile added the needs reproduction needs reproducible example to illustrate the issue label Apr 23, 2024
Copy link

ionitron-bot bot commented Apr 23, 2024

This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed.
Please see the Contributing Guide for how to create a Sample App.
Thanks! Ionitron 💙

@ionitron-bot ionitron-bot bot removed the triage label Apr 23, 2024
@Ionitron Ionitron added needs reply needs reply from the user and removed needs reply needs reply from the user labels Apr 23, 2024
@jcesarmobile jcesarmobile added the needs reply needs reply from the user label Apr 23, 2024
@wif70068
Copy link
Author

wif70068 commented May 1, 2024

We are not able to reproduce it without setting a debug point

@wif70068 wif70068 closed this as not planned Won't fix, can't repro, duplicate, stale May 1, 2024
@Ionitron Ionitron removed the needs reply needs reply from the user label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs reproduction needs reproducible example to illustrate the issue
Projects
None yet
Development

No branches or pull requests

3 participants