Andrei

We're getting this issue now across all our apps. It happens way too often. We may have to think to move away from code push or investigate ways to host...

@snowpardx absolutely. I'll let you know once it's resolved on my end. Are you guys seeing the issue on your end? And is it under investigation?

@snowpardx we've been having issues with code-push throughout the day. We've checked recently and seems like all the issues are gone now. The code-push is now working as expected for...

@snowpardx @VrajSolanki I can confirm that the issue is back this morning. It was working well last night which makes me think, if it's simply a high load issue. Are...

@VrajSolanki yes, it's not working at all. It's hurting our business badly, especially considering it's been down for couple days now. Customers are seeing an older app version because updates...

@tedkimzikto :) easy to say, we have about 100 apps that we'd need to deploy.

@tedkimzikto it was green all day yesterday. It doesn't reflect the real status of the service as far as I can see

@snowpardx The issue is clearly periodic. Right now code-push works very well for me. If the issues start to happen again tomorrow morning, it would support this theory. Therefore I...

very strange.. the version 3.1.1 works well for me. It seems like it's a parsing error for when the response is received from the APN server. I wonder what it...

Good question. You can pass a different serializer into the senders. Just override it here: https://github.com/andrei-m-code/net-core-push-notifications/blob/4f46d6003e2f8920890d69bf5cbd4e4931db3a20/CorePush/Serialization/DefaultCorePushJsonSerializer.cs#L24 The motivation behind having it camel case is that firebase and apple expects lower...