Home / Companies / Expo / Blog / Post Details
Content Deep Dive

Push notification receipt IDs will change string formats

Blog post from Expo

Post Details
Company
Date Published
Author
James Ide
Word Count
134
Company Posts That Month
3
Language
English
Hacker News Points
-
Post removed?
No
Summary

The Expo push notification service uses receipts with unique IDs to confirm whether notifications were correctly received by underlying providers like APNs and FCM, or if there was an error. Traditionally, these receipt IDs were UUIDv4 strings, but starting April 8, there will be an experimental switch to UUIDv7 strings. This change is not expected to impact code that treats receipt IDs as opaque strings, but developers are being notified to avoid relying on undocumented details, such as assuming receipt IDs will always be UUIDv4 or even a UUID, with the only assurance being that they will remain as strings.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.