Countly / Countly/countly-server

Allow Testing Push Notifications without Enterprise License

Open
#4,593 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
5.9k
Forks
981
Avg merge
18h 51m
Merged PRs (30d)
49

Description

Allow Testing Push Notifications without Enterprise License

Expected Behavior

It would be very useful if Countly allowed testing of push notifications in development without requiring an enterprise license. This would enable validation of push functionality during development before deploying to production.

Current Behavior

Currently, sending push notifications in Countly requires an enterprise license, even just for testing purposes. This blocks developers from properly testing push notifications during development.

Possible Solution

Provide the ability to send a limited number of push notifications (e.g. 10 per day) without an enterprise license, only for development/testing purposes. This would allow proper validation of push functionality before deploying to production with a full enterprise license.

Steps to Reproduce

Sign up for a Countly account with yearly billing and no enterprise license
Try to send a push notification from the dashboard or API
Receive an error that push notifications require an enterprise license

More Details

As a developer using Countly, having the ability to test push notifications during development is critical for me before deploying my application to production. Requiring an enterprise license just for testing is a blocker during development. I would love to have a limited push notification ability without enterprise licensing so I can properly test and validate push functionality in dev environments.

Please consider adding this ability! Let me know if any other details would help or if you need clarification. Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the push-notification flow from the dashboard and API, including where the enterprise-license error is produced. Define the development/testing limit and verify that limited test sends work without an enterprise license while regular production sending remains protected.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.