Repository navigation
APNSMessage#collapse_id parameter rejected in create_campaign despite being documented #3324
Description
Activity
- addedbugThis issue is a bug.This issue is a bug.needs-triageThis issue or PR still needs to be triaged.This issue or PR still needs to be triaged.
on Dec 11, 2025 Hi! Thanks for submitting this issue. We'll investigate. Did the previous version of pinpoint accept the
collapse_idparam?- addedinvestigatingIssue is being investigatedIssue is being investigatedand removedneeds-triageThis issue or PR still needs to be triaged.This issue or PR still needs to be triaged.
on Dec 11, 2025 Hi! Thanks for submitting this issue. We'll investigate. Did the previous version of pinpoint accept the
collapse_idparam?Hello, thanks.
We try only on the 103 and 116 release.Hi! The
CreateCampaignparameters come from the service team's model that we use to generate the SDK.I noticed the Campaign documentation doesn't show
CollapseIdunderAPNSMessage, but the Message documentation does include it underAPNSMessage. I'll cut a ticket to the service team to clarify this discrepancy and get back to you.Hi! I received a response from the Pinpoint service regarding this issue:
This is expected behavior. Campaigns do not support the
collapse_idparameter, whereas direct messages do. These are two different resources/APIs with different capabilities. Additionally, campaign functionality is on the path to deprecation, so this support will not be considered.
We recommend migrating to the newer messaging APIs: https://docs.aws.amazon.com/pinpoint/latest/userguide/migrate.htmlHope this clarifies the discrepancy. If you have additional questions about Pinpoint service
functionality, you can reach out to the service through via Contact Us in the migration guide linked above.- addedservice-apiGeneral API label for AWS Services.General API label for AWS Services.response-requestedWaiting on additional info and feedback. Will move to "closing-soon" in 7 days.Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.and removedinvestigatingIssue is being investigatedIssue is being investigatedbugThis issue is a bug.This issue is a bug.
on Dec 30, 2025 This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.
- addedclosing-soonThis issue will automatically close in 4 days unless further comments are made.This issue will automatically close in 4 days unless further comments are made.
on Jan 10, 2026 - Reacted by Juli Tera
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
When using Aws::Pinpoint::Client#create_campaign with an apns_message containing collapse_id, the SDK raises an ArgumentError even though collapse_id is a documented parameter for APNSMessage.
Regression Issue
Expected Behavior
The
collapse_idparameter should be accepted and passed to the Pinpoint API, which would then set theapns-collapse-idheader when sending the push notification to APNs.Current Behavior
The SDK raises an
ArgumentErrorbefore making the API call:Reproduction Steps
Possible Solution
No response
Additional Information/Context
The CollapseId parameter is documented in the AWS Pinpoint API reference for APNSMessage
The collapse_id parameter works correctly with send_messages endpoint
The parameter is essential for iOS notification grouping/replacement via the apns-collapse-id APNs header
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
aws-sdk-pinpoint 1.116.0
Environment details (Version of Ruby, OS environment)
ruby 3.4.7, multiple env (osX, linux)