Hey there!
We are using FCM to do some content updates on our iOS app. We have pushes that use content-available: 1 and some that don't.
(sorry for the code formatting)
The ones that *don't use it* are working fine, but the ones that use it are returning with:
{'error': {'code': 400,
'message': 'Request contains an invalid argument.',
'status': 'INVALID_ARGUMENT',
Now, by testing stuff around i was able to track this down to exactly "content-available" with iOS tokens. Android works perfectly:
In [145]: test = {'data': {'test': '1'}, 'token': android_token, 'apns': {'payload': {'aps': {'content-available': 1}}}}
In [146]: await sender.send_data_to_firebase({'message': test})
now with ios:
In [147]: test = {'data': {'test': '1'}, 'token': ios_token, 'apns': {'payload': {'aps': {'content-available': 1}}}}
In [148]: await sender.send_data_to_firebase({'message': test})
and if i remove the apns/aps option from the ios call, it works as expected.
Has anyone seen this?