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

channelType, Address and optOut removed from v6, Alternative method to set these? #13386

Closed
3 tasks done
soplan opened this issue May 15, 2024 · 7 comments
Closed
3 tasks done
Labels
Analytics Related to analytics duplicate If marked with duplicate, issue will be closed & original will be added for traceability feature-request Request a new feature

Comments

@soplan
Copy link

soplan commented May 15, 2024

Before opening, please confirm:

JavaScript Framework

React

Amplify APIs

Analytics

Amplify Version

v6

Amplify Categories

analytics

Backend

Other

Environment information

# Put output below this line


Describe the bug

In v5 I was able to set channelType, optOut and address.

With v6 I can't... all my users on our react website are registered as channelType "APN" with a blank address..

Because of this, We can't use either Journeys or Campaigns. Because this requires an address and EMAIL as channeltype in our case...

image

So is there a workaround or something to set the channelType to EMAIL and address?
I couldn't find it in the docs...

Expected behavior

Be able to set channelType, OptOut and Address using v6 library

Reproduction steps

Install v6.

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line


aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

Not using amplify push/pull, only the library.
Backend is set-up through CDK

@soplan soplan added the pending-triage Issue is pending triage label May 15, 2024
@cwomack cwomack self-assigned this May 15, 2024
@cwomack cwomack added the Analytics Related to analytics label May 15, 2024
@mohammedsahl
Copy link

+1 we're facing the same issue

@ashwinkumar6
Copy link
Contributor

Hi @soplan @mohammedsahl
Thanks for opening this ticket. Can you elaborate a bit more on the use case for the usage of channelType ,OptOut and Address in v6. These options were removed since they don't impact analytics endpoint.
doc reference

@ashwinkumar6 ashwinkumar6 added pending-response Issue is pending response from the issue requestor pending-triage Issue is pending triage and removed pending-triage Issue is pending triage labels May 23, 2024
@mohammedsahl
Copy link

Hey @ashwinkumar6. We use optOut to know if a user has opted out of receiving messages. We have pinpoint journeys which depend on knowing if the endpoint channelType is email.

All we get now is that an endpoint is of APNS channelType which I assume is apple push notification service? Anyway that isn't very useful for our purposes.

@soplan
Copy link
Author

soplan commented May 24, 2024

@ashwinkumar6

we use journeys and they depend on the channektype “email” and we use campaigns to send newsletters which also requires this channeltype. Without that channeltype the endpoint is not eligible for sending emails.

OptOut is by default set to ALL when endpoint is created. For sending emails we have to set this to NONE.

What does this even mean?
“These options were removed since they don't impact analytics endpoint.”

I really do not understand that sentence in the docs. Clearly these options are very much required.

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue requestor label May 24, 2024
@hisham
Copy link

hisham commented May 29, 2024

+1. This is a regression from v5. We are trying to update to v6 but without this feature we can't...

@mohammedsahl
Copy link

Hey @ashwinkumar6 would you have any updates on this?

@cwomack cwomack added duplicate If marked with duplicate, issue will be closed & original will be added for traceability feature-request Request a new feature and removed pending-triage Issue is pending triage labels Jun 4, 2024
@cwomack
Copy link
Contributor

cwomack commented Jun 4, 2024

@soplan, @hisham, @mohammedsahl

Just wanted to let you all know that we've reviewed this and the related #12721 internally to assess this as a migration blocker from v5 to v6 at this point. We had made the decision to remove the address, optOut, and channelType options in v6, so that's why we're marking this a feature request (and not a bug).

I'll also be consolidating this issue into the older #12721 to ensure we are consolidating the context/feedback, so please feel free to add any relevant comments on that older issue and give it a "thumbs up" for traction.

@cwomack cwomack closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
@cwomack cwomack removed their assignment Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Analytics Related to analytics duplicate If marked with duplicate, issue will be closed & original will be added for traceability feature-request Request a new feature
Projects
None yet
Development

No branches or pull requests

5 participants