Open jrconlin opened 4 years ago
Ok, so this is a really weird one. Autopush is plenty clear about only allowing valid content-encoding
headers through and gleefully returns 400 if it gets something bad.
autopush should not let a blank 'con' go through unless the message has no data. Working with @jonalmeida to sort out what's going on here.
Client was dropping some messages that don't have
con
data, which can happen withaes128gcm
encoded data content. We should not include empty fields if they're optional.