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]: OneSignal SDK 5.1.0 - Connection Error: "nw_resolver_start_query_timer_block_invoke [C1.1.1] Query Timeout #850

Closed
2 of 3 tasks
burhanaksendir opened this issue Mar 1, 2024 · 1 comment

Comments

@burhanaksendir
Copy link

burhanaksendir commented Mar 1, 2024

What happened?

I am using OneSignal SDK version 5.1.0, and consistently encountering the error "nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for api.onesignal.com:443" in the application logs. This error indicates a connection issue with the OneSignal API.

Steps to reproduce?

Launch the application.
Check the logs for the error message "nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for api.onesignal.com:443."

What did you expect to happen?

I expected the OneSignal SDK to function stably without encountering the "nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for api.onesignal.com:443" error.

OneSignal Flutter SDK version

5.1.0

Which platform(s) are affected?

  • iOS
  • Android

Relevant log output

nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for api.onesignal.com:443
nw_resolver_start_query_timer_block_invoke [C2.1.1] Query fired: did not receive all answers in time for api.onesignal.com:443

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jennantilla
Copy link
Contributor

Hello there--apologies that this issue was missed.

This could be caused by a number of things, including Network Instability, DNS Issues, or a Firewall.

After you check these settings, please update to our latest SDK. If you are still having problems, please create a new issue with a debug log and we'll be happy to help investigate further!

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

No branches or pull requests

2 participants