Allow Testing Push Notifications without Enterprise License
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
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.
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!
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 981
- Avg merge
- 19h 6m
- Merged PRs (30d)
- 52
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Countly/countly-server
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Countly/countly-server#7775 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Countly/countly-server#6891 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Countly/countly-server#5777 · 1 comment ·
Maintainers usually reply within 1 day
-
Hardware specsOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Countly/countly-server#5665 ·
Maintainers usually reply within 1 day
-
ARM64 SupportPossibly taken @andreialecu claimed this 257 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Countly/countly-server#5421 · 10 comments · 5 reactions ·
Maintainers usually reply within 1 day
All issues in Countly/countly-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/harper#3299 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
osmlab/name-suggestion-index#12992 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-government-design-system/ogds-elements#199 ·
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Document annotations cannot anchor visible code after a shorter or different fenced-code markerOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#16898 ·
Maintainers usually reply within 1 day