Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAT-1788 Add amazon s2s docs #555

Merged
merged 4 commits into from
Dec 16, 2024
Merged

CAT-1788 Add amazon s2s docs #555

merged 4 commits into from
Dec 16, 2024

Conversation

vlopezferrando
Copy link
Contributor

Motivation / Description

Docs for configuring Amazon real-time notifications.

Changes introduced

Added Amazon s2s instructions page and link it from "Platform server notifications" index page.

Linear ticket (if any)

https://linear.app/revenuecat/issue/CAT-1788/create-docs-for-amazon-s2s

Additional comments

Do not merge while this functionality is not available for everyone, or set it as beta and tell users to request access.

Copy link

Preview this PR here: https://dev-docs.revenuecat.com/pr-555/

Copy link
Contributor

@tiinanguyen tiinanguyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure to also add the page to the sidebars.js file here

Comment on lines 11 to 12
Amazon Appstore Real-time Notifications only work if the receipt exists in RevenueCat when the event is dispatched from Amazon Appstore. If the receipt doesn't exist, the event will fail.
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this true that the event will fail? Or will it be ignored? It'll be good to double check if Amazon has some sort of notification disablement if a certain threshold of notifications fail to deliver.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, it will just be ignored, and we don't send any error code to Amazon. I have updated the copy, but feel free to edit it further.

Comment on lines 35 to 36
7. In the RevenueCat dashboard, you should see a **Received at** timestamp for the endpoint too.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does Amazon send over a test notification?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also be explicitly here that it's a "Last received at"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does Amazon send over a test notification?

Yes, they do, they send a SubscriptionConfirmation message right away.


## Setup Instructions

1. Navigate to your **app settings** in the RevenueCat dashboard by selecting your app from **Project Settings > Apps**.
Copy link
Contributor

@tiinanguyen tiinanguyen Dec 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be explicit here and say "Navigate to your Amazon app settings"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@vlopezferrando
Copy link
Contributor Author

Make sure to also add the page to the sidebars.js file here

Right! Done.

@vlopezferrando vlopezferrando changed the title DO NOT MERGE CAT-1788 Add amazon s2s docs CAT-1788 Add amazon s2s docs Dec 16, 2024
@vlopezferrando vlopezferrando merged commit a136339 into main Dec 16, 2024
3 checks passed
@vlopezferrando vlopezferrando deleted the amazon-s2s branch December 16, 2024 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants