Airship failing HTTP requests to backend service

Follow

Hi,

Thank you for contacting the support.

Could you please make sure that this Named User option is enabled:

You can find this by going to the Settings page -> Named Users.

Best regards

Ok thx I will check!

I understand that you are experiencing a large number of failing HTTP calls to the endpoint https://device-api.urbanairship.com/api/contacts/resolve/ with a 403 Forbidden response. While it doesn't seem to affect push notification delivery, it is still causing annoyance in your monitoring.

To disable these calls during library start in iOS and Android, you may need to provide more information about the specific library or SDK you are using to interact with the Urban Airship API. Each library or SDK may have its own configuration options or initialization methods that allow you to disable certain calls. 

When encountering issues with HTTP requests from an airship (or any other application) to a backend service, there could be several potential reasons for the problem. Here are some common troubleshooting steps to identify and resolve the issue: Ensure that the airship has a stable network connection to reach the backend service. Test other network-dependent features to see if the problem is specific to HTTP requests or a broader network issue. Verify that the backend service is up and running. You can check the service status and logs to see if there are any errors or outages. Confirm that the airship is using the correct URL to reach the backend service. A typo or incorrect URL could lead to failed requests. If the backend service requires authentication, ensure that the airship is providing the correct credentials or authentication tokens. Check if there are any network restrictions, firewalls, or security groups blocking the airship's access to the backend service.....

Thank you for reporting the issue with frequent HTTP 403 Forbidden responses for Airship HTTP calls to the endpoint https://device-api.urbanairship.com/api/contacts/resolve/. While these calls might not directly impact push notification delivery, their presence in monitoring is concerning. To address this, first ensure that your configuration settings and API credentials are accurate and up to date. 

When your Airship (also known as The Skeld) game is experiencing issues with failing HTTP requests to a backend service, it can be challenging to pinpoint the exact cause without more information. However, you can follow a systematic approach to troubleshoot and resolve the issue:

1. Check Server Status:

   • First, ensure that your backend service is up and running without any issues. Check the server logs and monitoring tools to confirm its status.

2. Review Error Logs:

   • Examine the error logs on both the Airship and the backend service to identify any error messages or patterns that might provide clues about the nature of the failures.

3. Network Connectivity:

   • Verify that the Airship server has a stable and uninterrupted network connection to the backend service. Network issues can lead to failed HTTP requests.
   • Regards; toonkor

The frequent occurrence of failing airship HTTP calls to the endpoint https://device-api.urbanairship.com/api/contacts/resolve/ with a HTTP 403 Forbidden response is indeed causing a notable volume of errors in our monitoring system. Despite these failures, it's important to note that the push notification delivery is not adversely affected. However, we recognize that these consistent errors are an undesirable aspect in our monitoring.

Regard,

blacktiedetailing