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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug Report: Tenant Feature not working for selecting Providers #5345

Open
2 tasks done
gowtham18k opened this issue Apr 1, 2024 · 1 comment
Open
2 tasks done
Labels

Comments

@gowtham18k
Copy link

馃摐 Description

Currently, I'm facing a problem. I have 2 diff FCM providers. There is an option to add conditions using the tenant. I'm still testing that but it is not working. Even though I added the tenant key in the trigger Api notifications triggered with two providers.

馃憻 Reproduction steps

  1. Create Two Firebase Providers for 2 different apps.
  2. Create Individual Tenants for Both
  3. Add the Provider Condition using the tenant identifier
  4. Create a workflow with Push notification setp
  5. Create a subscriber and add two diff FCM token for a single subscriber
  6. Trigger the workflow for the created subscriberdifferent

馃憤 Expected behavior

if the provider conditions are added and the event trigger tenant is also added then Notification needs to be received in a particular app.

馃憥 Actual Behavior with Screenshots

Notification is receiving two apps eventhough tenant conditions are added.

Novu version

Novu SaaS

npm version

NA

node version

NA

馃搩 Provide any additional context for the Bug.

No response

馃憖 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find a similar issue

馃彚 Have you read the Contributing Guidelines?

Are you willing to submit PR?

None

Copy link

linear bot commented Apr 1, 2024

@gowtham18k gowtham18k changed the title 馃悰 Bug Report: Tenant Feature not working for selecting the FCM Provider 馃悰 Bug Report: Tenant Feature not working for selecting Providers Apr 1, 2024
@github-actions github-actions bot added the triage label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant