Hi @ge-af 👋

I would agree with your conclusion, but actually this issue wasn’t a problem for our ~20k users project 3 month ago. We were using v6.2.60 that time and keeping the dependency up-to-date since then. Now, this report is always on top of the Sentry / Firebase / whatever else bug tracking system table. Furthermore:

This issue looks related to internet connection issues.

The app is used to send multiple HTTP requests during the start time, including the appsflyer initialization and conversion data retrieval. It works OK, but produces these failed to connect errors for some reason.

Please investigate, since several bug tracking systems have limited amount of trackable errors in its free plans, meaning the smaller projects may suffer from such type of issues. Thank you.

I would not agree to close this issue. We have the same in Sentry logs It started to appear a year ago. And now we have 223k error events in Sentry logs about that. Right now we’re using version 6.3.50 with RN 0.60.5 The most OS appeared is Android, few on iOs Users mostly from US

Facing same issue our in production application.

I was facing same issue on react-native 0.62.2 and react-native-appsflyer 6.4.0 in South Korea.

Sentry shows 2 different message like others.

• Unable to resolve host "inapps.appsflyer.com": No address associated with hostname
• Failed to connect to inapps.appsflyer.com/0.0.0.0:443

I still don’t know what’s causing that issue but it seems changing targetSdkVersion to 30 significantly lowered the occurence of this error.

BTW, can anyone help me understanding how this sdk is initialized and track new install count and so on? I’m currently using appsflyer and codepush.

When app is launched, root component will mounted and sdk will be initilized. After that codepush checks for update. if there is one, js bundle will be switched and the exact same process will be repeated, calling appsFlyer.initSdk in one launch. would that be problematic?

Same issue for me too.

Error: Failed to connect to inapps.appsflyer.com/:::443

Because of this issue events are not reflected on the AppsFlyer dashboard.

I am using “@ionic-native/appsflyer”: “^5.16.0”, “cordova-plugin-appsflyer-sdk”: “^6.3.0”,

Did not see any resolution for this anywhere. Is this issue closed?

Confirm the issue. Should be reopened

Error: Failed to connect to inapps.appsflyer.com/0.0.0.0:443

“react-native-appsflyer”: “^6.5.20”

Hi all,

This issue looks related to internet connection issues. This is usually a networking problem on the device itself and not so related to the SDK specifically. It seems this is a DNS issue, it unable to resolves the hostname to the proper IP address and that’s why the IP is not assigned (0.0.0.0).

would it be possible to check if the user has internet before the error is triggered? I’m having the same problem.

Failed to connect to inapps.appsflyer.com/0.0.0.0:443

Which is the network issue exactly?

Because on our logs our app is able to do a codepush update, and fetch from our API mutliple times with 200 status responses before getting this error or this other one:

error: Unable to resolve host "inapps.appsflyer.com": No address associated with hostname, 

Can this issue be reopened? I do not see a resolution or proposed workaround

@ge-af does SDK have retry mechanism to recover from this?

Hi I’m also facing this issue mostly Failed to connect to inapps.appsflyer.com/0.0.0.0:443 Unable to resolve host “inapps.appsflyer.com”: No address associated with hostname Error: com.appsflyer.sdk.network

My app resides on Indonesia, some of them using wifi broadband or mobile… It looks like the DNS not propagated properly on some ISP.

Here some ISP/Mobile Carriers from my IP Tracing PT Telkom Indonesia (Major Mobile Provider in Indonesia) PT Data Buana Nusantara Biznet Networks PT Indosat (Major Telco In Indonesia) PT Gayatri Lintas Nusantara PT. Eka Mas Republik

Non Indonesia ISP The University of Edinburgh

The experiences are not consistent because some of user (our tester) with the ISP mentioned above did not experience the error. It really looks like a unfinished/unproper DNS propagation

Cheers