Large number of console errors

[pouyaemami]

SDK version: 5.0.1

Are logs available?

[CIO] CustomerIO DataPipelines module is initialized and ready to use
console.js:654 [CIO] CustomerIO MessagingPushFCM module is initialized and ready to use
console.js:654 [CIO] CustomerIO SDK is initialized and ready to use
console.js:654 [CIO] Customer.io instance initialized successfully from app
console.js:654 [CIO] updating device attributes: {device_os=36, device_model=Pixel 7 Pro, device_manufacturer=Google, app_version=3.4.0, cio_sdk_version=5.0.1, device_locale=en-CA, push_enabled=true}
console.js:654 [CIO] identify profile with identifier Zr5b9wABnjaTfeF8h0As16gPYJz1 and traits {name=******, email=******}

Describe the issue
I am seeing a large number of console errors after implementing the SDK which appear when the app is idle or when the app is foregrounded. The number of errors shown in the screenshot is from about 5-10 minutes of idle activity.

Screenshots

Additional context
I can see events come through to the dashboard on Customer.IO so I know tracking is working so I am not sure why I am seeing these errors.

Here's a list of the errors I am seeing:

• [CIO] Error uploading events from batch file fileUrl="..." msg=Unable to resolve host "cdp.customer.io": No address associated with hostname
• [CIO] Unable to resolve host "cdp.customer.io": No address associated with hostname

[mahmoud-elmorabea]

Thanks for the report @pouyaemami !

Does this happen when you put the app to the background temporarily? If so, that's a known limitation on Android 15+ where network requests are blocked by the OS if the app is stopped (or in the background).

This doesn't affect tracking as you have confirmed because the SDK retries to flush these events to our servers till it succeeds, so when the app moves back to the foreground or re-opened, those events will be flushed.

You can configure the logging level to only show errors or disable them to avoid cluttering your logs with these expected errors.

[pouyaemami]

@mahmoud-elmorabea thanks for getting back to me. Yes this is happening when the app is in background mode as you've mentioned. It would be great to have this error not logged if it is a known issue on Android 15+. I'm not sure I want to filter out all the [CIO] logs since it will potentially eat up valid errors.

[mahmoud-elmorabea]

I will create a task for our team to filter out these logs since they might not be very actionable for SDK integrations. Apologies for the inconvenience 😇

[pouyaemami]

Thanks so much!