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

[ghost]

Report

Plugin Version

6.3.20

On what Platform are you having the issue?

Android

What did you do?

Launch application and init sdk via appsFlyer.initSdk({ devKey: ****, isDebug: false, });

What did you expect to happen?

AppsFlyer successfully connect to server

What happened instead?

AppsFlyer log error about problem with connection There are our two Sentry reports 1) Error: Failed to connect to inapps.appsflyer.com/:::443

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

Please provide any other relevant information.

We have hundreds error events in our sentry reports. This error started two months ago. Also we have no more full statistic in our AppsFlyer dashboards.

[anshzinc]

Facing same issue our in production application.

[ge-af]

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).

[artyorsh]

Hi @ge-af :wave:

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.

[ge-af]

Hi @artyorsh

Thanks for your valuable feedback!

I'm checking it again with our R&D and DevOps teams to see if there were any changes on our side regarding any DNS or Server issues that may have started in the last few weeks/months.

Can you please notice if there is something specific regarding the users who gets this networking errors (if possible) - Any specific regions/countries or any specific Android OS versions this is coming from?

If possible also to list all exception occurrences of this error (SSLException, SSLHandshakeException, etc.) that may be visible under any Analytics provider (Sentry, Firebase Crashlytics, etc.) and I'll forward it to our R&D team to further investigate.

[artyorsh]

Thank you for the quick response @ge-af

Any specific regions/countries

The app is limited to run in Germany. I'm not sure the error report can be informative in this case, since its stack trace doesn't show anything interesting. However, see the link. This one was reported ~30k times during last 3 months.

I can't be sure it could be related to the region since I also see the error occurs also in Belarus in our dev environment. See report. In some occurencies it's reported with Unable to resolve host "inapps.appsflyer.com": No address associated with hostname message.

any specific Android OS versions

It's mostly reported on Android. Unfortunately, there is no specific OS version where this issue occurs. On iOS however I may suppose that it is reported with a different message. Supposedly, Network failure.

There is one more interesting report I found while reviewing the whole error table (Android 9, Samsung SM-G950F): https://sentry.io/share/issue/e0e217226eaa450597a82a85af101709

I'll check these errors in detail to see if I can find anything else from there.

[ge-af]

Hi @artyorsh

We tried to test it from Belarus and Germany and got the DNA resolution and everything is working on our side. Do you have any way to identify which ISP/Mobile carriers are being used by the users with those faulty errors? If so, we can continue to try and take it with AWS Support.

[bondanherumurti]

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

[pebehb]

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

[eatnug]

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?

[dimadeveatii]

We also see this issue happening sometimes, on both platforms, Android and iOS. We believe this is due to a network error.

Question: is the sdk supposed to work in offline mode? Suppose I'm offline, track some events, then return to the app in an hour with stable network connection. Will appsflyer re-submit the failed events?

[pebehb]

We also see this issue happening sometimes, on both platforms, Android and iOS. We believe this is due to a network error.

Question: is the sdk supposed to work in offline mode? Suppose I'm offline, track some events, then return to the app in an hour with stable network connection. Will appsflyer re-submit the failed events?

Agree with you: there is network issue.

I have another question: should this affect on my App or not ? I believe - NOT

[diegodorado]

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, 

[diegodorado]

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

[djw27]

We're seeing multiple variations of this at really high rates which can't really be explained by internet connectivity issues as the error is preceded by successful requests to other APIs in our case.

Variations we're seeing:

Unable to resolve host "inapps.appsflyer.com": No address associated with hostname Failed to connect to inapps.appsflyer.com/0.0.0.0:443 Failed to connect to inapps.appsflyer.com/:::443 java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Also worth mentioning we're almost exclusively seeing this on Android devices

[rusakovic]

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"

[anuragshahi9911]

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?

[raquel-nobre]

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

[LydGol90]

Hi. We have also been battling with this issue, however I realised that for us it was due to our segment integration set up pointing to an app id for an app that no longer existed. (I had created it purely for debug testing). I have noticed that it can take some time after setting up a new app in appsflyer before it becomes "available" to the SDK and so was also seeing it in these cases. I've not confirmed but it may also happen if integration is turned off in Segment. Just posting this here in case this helps anyone else.

[sekoyo]

I have checked that Segment is using the correct App IDs and AppsFlyer devkey but also getting 1000s of these errors, all other network requests are fine 🤔 Happens on both iOS and Android

[givehug]

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

[WouterFlorijn]

@ge-af @amit-kremer93 can anything be done here. We're seeing this error being reported thousands of times for hundreds of users per day. It doesn't seem to crash our app, but it's still cluttering our error monitoring and potentially causing missing analytics data.

This is clearly an AppsFlyer issue, since it's happening on any platform or device, and way more often than other connectivity issues (which we also monitor). Therefore it cannot be dismissed as a device connectivity issue. Please reopen.

[amit-kremer93]

@WouterFlorijn did you open ticket to our support team? once you open a ticket we can investigate your problem more easily and to find what caused it.

[Norfeldt]

@ge-af would it be possible to keep this issue open until it has been fixed (and then close it)?

[VaidyaAkhil-Groww]

Hello, please revert on this issue, a large number of our users are also facing this (~ 200K events with ~60K users impacted) We have found no correlation with Devices, OS, OS versions, manufacturers, and others.

Can we check on AppsFlyer's end how many such requests are failing

Different error messages that we are getting:

java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

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

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

    failed to connect to inapps.appsflyer.com/18.161.125.129 (port 443) from /56.198.3.219 (port 45040) after 10000ms

[gestshb]

Hi,

I'm having the same issue as you. I contacted support and they said that the Connection error 443 is most likely an issue with the internet connection. This is usually a networking problem on the device itself. The device on which the test is performed doesn't have a valid internet connection, or the request fails due to DNS issues.

They also said that they have seen cases where the network prevents connecting to the AppsFlyer server. Please check the network connection/VPN connection (if using) and make sure that Adblocker or Firewall is not preventing access.

Here are some additional steps you can try:

Restart your device. Check your internet connection. Disable any Adblockers or Firewalls. Try using a different browser. Try using a different device. If you are still having problems, please contact support again.

Finally, a solve my problem! I was able to fix the issue by disabling my Adblocker. I hope this helps you as well.

[VaidyaAkhil-Groww]

We also connected with the AppsFlyer team for the same issue. And were able to reproduce it using any Adblocker. However, this was not a fatal issue for us (App did not crash and the user wasn't blocked in any way), hence we suppressed the issue at our end

[NarayanFH]

Issue, is still there for a specific device. I don't know how the IP or DNS is not valid to get the response of: Failed to connect to zf8phv-cdn-settings.appsflyersdk.com/:::443

[glockjt]

Same issue here, has there been any update @ge-af? TIA

[asfaqehussain]

I am still facing the issue in my app in React native

[DominikVavra]

Is there anything new about this problem ? Its 2024 and it seems that problem is still here.

Framework: React native Appsflyer version: 6.9.2

Error:

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

Its still the same scenario. App is doing several API requests at the same time as AppsFlyer SDK inicialization. All other requests are OK (200) except appsflyer one. Our sentry is full of these errors. Hundreds per day. Is there any new solution we can try ?

I don't want accept the answer that it is a network issue. As i said - ALL other requests are fine. There is no retry mechanism ? so it will try to reach the url few times and after that it will fire the error? Or can we somehow suppress the error? Make it warning only.

Thank you