500 Error on Push notification calls


Currently we are using urban airship API (https://go.urbanairship.com/api/push/) to send push notifications from the client side, but we are receiving internal server errors intermittently for the last couple of days.

Here's the stack trace of the error;

The remote server returned an error: (500) Internal Server Error.

at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <11aab24ad7644cfb92395f748cb77622>:0
at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <7f0c11dc43cc4a24af02cc69a79def10>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <7f0c11dc43cc4a24af02cc69a79def10>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <7f0c11dc43cc4a24af02cc69a79def10>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <7f0c11dc43cc4a24af02cc69a79def10>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <7f0c11dc43cc4a24af02cc69a79def10>:0
at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <7f0c11dc43cc4a24af02cc69a79def10>:0

Any pointers on how to fix this issue? Thanks.

Didn't find what you were looking for?

New post


1 comment

  • Hi Michael,

    While we make every attempt to allow and process connections to our servers, these errors do occur time to time. We suggest implementing a system of retry with exponential backoff in most situations.

    Please take a look at our document Best Practices for 500 and 503 errors for more detailed information on this topic. 

    Comment actions Permalink

Please sign in to leave a comment.