The docs have specified "push-tickets" to be the response that is returned when we push notifications to the Expo servers. And that "push-receipts" are receipts generated once Expo enqueues the notifications to FCM and APNs. These receipts are queried with the IDs present in the push-tickets.
In publish_internal() the push_tickets are named as receipts, which could lead to confusion while reading the documentation. Also check_receipts() takes in the push-tickets as a parameter, but is named receipts, which could lead to confusion. check_receipts() seems to suggest that the function is checking the receipts itself, when its actually querying Expo for the push-receipts.
Is this a necessary change ? If you think it is, i'll make a pull request.
Thanks :)
The docs have specified "push-tickets" to be the response that is returned when we push notifications to the Expo servers. And that "push-receipts" are receipts generated once Expo enqueues the notifications to FCM and APNs. These receipts are queried with the IDs present in the push-tickets. In
publish_internal()
the push_tickets are named asreceipts
, which could lead to confusion while reading the documentation. Alsocheck_receipts()
takes in the push-tickets as a parameter, but is named receipts, which could lead to confusion.check_receipts()
seems to suggest that the function is checking the receipts itself, when its actually querying Expo for the push-receipts.Is this a necessary change ? If you think it is, i'll make a pull request. Thanks :)