Incrementing a push notification badge number support coming soon?

[taufiq-husain]

How can I tell whether the open source server will support something or whether I should implement a solution myself? I noticed that on the detailed docs, it said that Parse server doesn't support iOS badge numbers yet. Does this mean it's coming soon? Could I please know when/how I can help to speed this particular part? My project needs to be live on the app store within a week and this part is the only broken part.

I've successfully set up cloud code and fixed up my iOS front-end codes to use the Parse server. Thank you guys so much for everything you're doing with this. Highly appreciate it!

[flovilmart]

As per the documentation it seems that the badge is supported: https://github.com/ParsePlatform/parse-server/wiki/Push#api

[anatolydwnld]

I think this ticket was about supporting Increment as the badge value(https://parse.com/docs/rest/guide#push-notifications-sending-options). Please, re-open.

[flovilmart]

Did you try badge: "increment" ? It should to the job

[taufiq-husain]

You can see in Parse's Push wiki, it says that this hasn't been implemented "yet". Link: https://github.com/ParsePlatform/parse-server/wiki/Push. That's why I was asking if/when/whether it'll ever be implemented...

[flovilmart]

Right.

[anatolydwnld]

Just to double check, I tested badge: "increment". Didn't work. There doesn't seem to be any mention of this in the source either. The wiki is correct in stating that this feature is not yet implemented.

[flovilmart]

PR is pending review

[taufiq-husain]

Hi,

I've updated my package.json file to "parse-server": "~2.1.4" but the "Increment" push notification feature doesn't seem to work still. I'm using the standard iOS APN system explained here: https://github.com/ParsePlatform/parse-server/wiki/Push. I deployed my code to my Heroku server by updating the package number but the push notification feature still doesn't increment. When I use the badge: 1 feature which works well but the increment feature doesn't. In fact, if I put the badge as "Increment", the badge doesn't update at all. What am I doing wrong? Did I not update the Parse server properly on Heroku? Do I need to do something more?

Thanks.

[taufiq-husain]

I've also updated using the instructions given here: #879

Any ideas why it's not working still @flovilmart ?

[flovilmart]

Can you run a query on _Installation to see if the badge value increments correctly? The badge increment is only for iOS devices, (deviceType=ios should be set on _Installation).

Also when you say not working at all, what do you mean?

[taufiq-husain]

I did. The badge is still showing zero.

Here is my package.json:

{
  "name": "parse-server-example",
  "version": "1.1.0",
  "description": "An example Parse API server using the parse-server module",
  "main": "index.js",
  "repository": {
    "type": "git",
    "url": "https://github.com/ParsePlatform/parse-server-example"
  },
  "license": "MIT",
  "dependencies": {
    "express": "~4.2.x",
    "kerberos": "~0.0.x",
    "parse": "~1.6.12",
    "parse-server": "~2.1.4"
  },
  "scripts": {
    "start": "node index.js"
  },
  "engines": {
    "node": ">=4.3"
  }
}

I'm using cloud code to send push notifications. As soon as I change the badge value to "1", it works. As soon as I change it "Increment", it stops showing any numbers. It just shows 0 for the receiving user's badge in the _Installation row.

Here is me updating my Parse Server:

Taufiqs-MBP:getlolapp Taufiq$ cd parse-server
Taufiqs-MBP:parse-server Taufiq$ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
Taufiqs-MBP:parse-server Taufiq$ git pull
Already up-to-date.
Taufiqs-MBP:parse-server Taufiq$ cd ..
Taufiqs-MBP:getlolapp Taufiq$ git commit -am "Testing"
[master d911f50] Testing
 1 file changed, 1 insertion(+), 1 deletion(-)
Taufiqs-MBP:getlolapp Taufiq$ git push heroku master
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 287 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 1 (delta 1)
remote: Git submodules detected, installing:
remote: Synchronizing submodule url for 'parse-server'
remote: Submodule path 'parse-server': checked out '75ae95815d30c99f67119301ef8619cbf0606cfe'
remote: 
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Using set buildpack heroku/nodejs
remote: -----> Node.js app detected
remote: 
remote: -----> Creating runtime environment
remote:        
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NPM_CONFIG_PRODUCTION=true
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote: 
remote: -----> Installing binaries
remote:        engines.node (package.json):  >=4.3
remote:        engines.npm (package.json):   unspecified (use default)
remote:        
remote:        Resolving node version >=4.3 via semver.io...
remote:        Downloading and installing node 5.7.1...
remote:        Using default npm version: 3.6.0
remote: 
remote: -----> Restoring cache
remote:        Loading 2 from cacheDirectories (default):
remote:        - node_modules
remote:        - bower_components (not cached - skipping)
remote: 
remote: -----> Building dependencies
remote:        Pruning any extraneous modules
remote:        Installing node modules (package.json)
remote: 
remote: -----> Caching build
remote:        Clearing previous node cache
remote:        Saving 2 cacheDirectories (default):
remote:        - node_modules
remote:        - bower_components (nothing to cache)
remote: 
remote: -----> Build succeeded!
remote:        ├── express@4.2.0
remote:        ├── kerberos@0.0.18
remote:        ├── parse@1.6.14
remote:        └── parse-server@2.1.4
remote:        
remote: 
remote: -----> Discovering process types
remote:        Procfile declares types     -> (none)
remote:        Default types for buildpack -> web
remote: 
remote: -----> Compressing...
remote:        Done: 20.5M
remote: -----> Launching...
remote:        Released v67
remote:        https://getlolapp.herokuapp.com/ deployed to Heroku
remote: 
remote: Verifying deploy... done.
To https://git.heroku.com/getlolapp.git
   e066c75..d911f50  master -> master