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

Query fired: did not receive all answers in time for graph.facebook.com:443 #2124

Open
5 tasks done
bonzoq opened this issue Oct 2, 2022 · 27 comments
Open
5 tasks done

Comments

@bonzoq
Copy link

bonzoq commented Oct 2, 2022

Checklist before submitting a bug report

Xcode version

14.0

Facebook iOS SDK version

15.0.0

Dependency Manager

SPM

SDK Framework

Core

Goals

I would like to track app installs and send custom events to Facebook Events Manager

Expected results

App installs tracked and custom events received in Facebook Events Manager.

Actual results

Installs are not tracked. Neither standard nor custom app events are received in Facebook Events Manager. I see the following error in xcode logs:

Query fired: did not receive all answers in time for graph.facebook.com:443

Full log:

2022-10-02 18:35:27.271639+0200 Appname7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.271946+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.287321+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C3.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.360958+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.361291+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.386177+0200 Appname7446[7446:2051891] [connection] nw_resolver_start_query_timer_block_invoke [C3.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.498069+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C7.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.498387+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C8.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2022-10-02 18:35:27.498540+0200 Appname7446[7446:2051894] [connection] nw_resolver_start_query_timer_block_invoke [C9.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443```

### Steps to reproduce

1. Create a new app in xcode.
2. Add Facebook SDK according to the installation guidelines.
3. Run app from Xcode.

### Code samples & details

_No response_
Amoon-123 referenced this issue Oct 3, 2022
Reviewed By: samodom

Differential Revision: D39942190

fbshipit-source-id: 7bb9fd40d6c26d60269e10754f525cf5594a01ec
@bonzoq
Copy link
Author

bonzoq commented Oct 3, 2022

@samodom would you be able to help?

@bonzoq
Copy link
Author

bonzoq commented Oct 4, 2022

Would you be ale to help @jawwad?

@bonzoq
Copy link
Author

bonzoq commented Oct 5, 2022

Is it possible to get any support from FB at all?

@tharwi
Copy link

tharwi commented Oct 9, 2022

Got the same issue in v14.1.0

@Krisdebo
Copy link

Krisdebo commented Oct 9, 2022

There's another topic about this bug #2085 . Not solved as well.

@tharwi
Copy link

tharwi commented Oct 10, 2022

It seems like events are fired if I directly set the configuration as below in the info.plist

  <key>FacebookAdvertiserIDCollectionEnabled</key>
  <true/>

But I want to get the user's consent and then mark it as true

@hannesjung
Copy link

Facing the same issue, did anyone find another solution where we can get the user's consent before enabling advertiser ID collection?

@tunminster
Copy link

I am facing the same issue. Have you guy sorted this out?

@Aqitaniya
Copy link

I have the same issue

@Ekahrb
Copy link

Ekahrb commented Jan 24, 2023

I have the same issue

@diegocuehdz
Copy link

Is there an update on this? Still happening as of February 13 2023

@Ozantunaa
Copy link

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

@pedrosolisgarcia
Copy link

pedrosolisgarcia commented Mar 1, 2023

Same here...

2023-03-01 14:33:47.682922+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:47.683252+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:48.071687+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:48.071966+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:48.710538+0100 <MyAppName>[5766:1781255] [connection] nw_resolver_start_query_timer_block_invoke [C7.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:48.969128+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C9.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-03-01 14:33:48.969544+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C10.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

No matter the config on Info.plist, these logs always appear

@Ozantunaa
Copy link

Ozantunaa commented Mar 1, 2023

Same here...


2023-03-01 14:33:47.682922+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:47.683252+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:48.071687+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C1.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:48.071966+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C2.1.2] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:48.710538+0100 <MyAppName>[5766:1781255] [connection] nw_resolver_start_query_timer_block_invoke [C7.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:48.969128+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C9.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

2023-03-01 14:33:48.969544+0100 <MyAppName>[5766:1781249] [connection] nw_resolver_start_query_timer_block_invoke [C10.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

No matter the config on Info.plist, these logs always appear

I created a new onesignal app and did everything from the beginning with the new certificates and improved.

@daveslutzkin
Copy link

Yeah these logs are so noisy, doesn't seem to impair functionality but it would be nice to get rid of them.

@calsmith
Copy link

Issue still happening even for a fresh project

@khitish2321
Copy link

Just started working on fresh project and I also ran into the same issue.

@dispersik
Copy link

same error

@daradonn
Copy link

try this :

If you are working on iOS 14+ do check this App tracking permission that is required for events tracking.

https://developer.apple.com/app-store/user-privacy-and-data-use/#permission-to-track

Also, while testing on real device (iOS) check if your device's facebook app "Allow Tracking" is allowed. You can do this by checking facebook's permissions from Settings.

REF: https://stackoverflow.com/questions/70833242/facbook-events-doesnt-works-on-ios

@Zee-93
Copy link

Zee-93 commented Apr 5, 2023

@daradonn thanks for you answer it's very helpful. By using your solution I successfully login with Facebook but not getting the callback in my app. I am getting following logs.

2023-04-05 14:46:31.521544-0400 Vooconnect[4972:837438] Connection 21: received failure notification
2023-04-05 14:46:31.521619-0400 Vooconnect[4972:837438] [connection] nw_flow_add_write_request [C21 24.43.25.241:9450 failed parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns, constrained)] cannot accept write requests
2023-04-05 14:46:31.521661-0400 Vooconnect[4972:837438] [connection] nw_write_request_report [C21] Send failed with error "Socket is not connected"

@cengizhankervanci
Copy link

The same error continues in the game I made in Unity. Anyone know the solution?

2023-05-09 20:27:24.148971+0300 MyApps[5672:1742969] [tcp] tcp_input [C2.1.1:3] flags=[R.] seq=1681785977, ack=3432364880, win=265 state=CLOSED rcv_nxt=1681785937, snd_una=3432364855
2023-05-09 20:27:24.159672+0300 MyApps[5672:1743019] [Client] Updating selectors after delegate addition failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 94 named com.apple.commcenter.coretelephony.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 94 named com.apple.commcenter.coretelephony.xpc was invalidated from this process.}
2023-05-09 20:27:24.475982+0300 MyApps[5672:1742970] [tcp] tcp_input [C6.1.1:3] flags=[R] seq=1579991797, ack=0, win=0 state=CLOSED rcv_nxt=1579991797, snd_una=1425097925
2023-05-09 20:27:25.387534+0300 MyApps[5672:1742974] [connection] nw_resolver_start_query_timer_block_invoke [C1.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-05-09 20:27:25.387707+0300 MyApps[5672:1742974] [connection] nw_resolver_start_query_timer_block_invoke [C2.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-05-09 20:27:25.966930+0300 MyApps[5672:1743019] [connection] nw_resolver_start_query_timer_block_invoke [C3.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-05-09 20:27:26.164896+0300 MyApps[5672:1742974] [connection] nw_resolver_start_query_timer_block_invoke [C4.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-05-09 20:27:26.164987+0300 MyApps[5672:1742974] [connection] nw_resolver_start_query_timer_block_invoke [C5.1] Query fired: did not receive all answers in time for graph.facebook.com:443
2023-05-09 20:27:26.165010+0300 MyApps[5672:1742974] [connection] nw_resolver_start_query_timer_block_invoke [C6.1] Query fired: did not receive all answers in time for graph.facebook.com:443

@emreakcan
Copy link

Same error on iOS, Flutter.
Seems like events are counted in the graph but not properly logged. Shows no events but says there is 2000 events in the graph.

@mwmw7
Copy link

mwmw7 commented Aug 27, 2023

try this :

If you are working on iOS 14+ do check this App tracking permission that is required for events tracking.

https://developer.apple.com/app-store/user-privacy-and-data-use/#permission-to-track

Also, while testing on real device (iOS) check if your device's facebook app "Allow Tracking" is allowed. You can do this by checking facebook's permissions from Settings.

REF: https://stackoverflow.com/questions/70833242/facbook-events-doesnt-works-on-ios

it works~!!!

@utkuzorlu
Copy link

@daradonn thanks for you answer it's very helpful. By using your solution I successfully login with Facebook but not getting the callback in my app. I am getting following logs.

2023-04-05 14:46:31.521544-0400 Vooconnect[4972:837438] Connection 21: received failure notification
2023-04-05 14:46:31.521619-0400 Vooconnect[4972:837438] [connection] nw_flow_add_write_request [C21 24.43.25.241:9450 failed parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns, constrained)] cannot accept write requests
2023-04-05 14:46:31.521661-0400 Vooconnect[4972:837438] [connection] nw_write_request_report [C21] Send failed with error "Socket is not connected"

Did you find a solution?

@MoElkilany
Copy link

I have the same issue here ?

nw_resolver_start_query_timer_block_invoke [C647.1] Query fired: did not receive all answers in time for mydga.dga.local:443

@rrsaikat
Copy link

The operation couldn’t be completed. (com.facebook.sdk.login error 304.)
[connection] nw_resolver_start_query_timer_block_invoke [C73.1.1] Query fired: did not receive all answers in time for graph.facebook.com:443

Same issue!

@landon2022
Copy link

I have a similar situation. This maybe because facebook was blocked in your region. Use a VPN and it may work again.

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

No branches or pull requests