In the old CocoonJS cloud the Local and Parse Push notifications weren’t separated and were both installed when installing the Parse Notification plugin. In the new Cocoon cloud we have separated both plugin so now you can install both if them separately. If any of them have been automatically migrated but you don’t really use it, you can uninstall it.


The Parse Notifications plugin will be migrated along with your application configuration when your projects are automatically migrated to the new Cocoon cloud so you should have all the plugins installed in the new Cocoon cloud already. To check if everything is correct go to the old CocoonJS cloud and check if you had the Parse Notifications plugin enabled.

Screen Shot 2016-01-19 at 14.12.31


Now go to the new Cloud and check that the Parse Notifications plugin have been correctly migrated (along with the Local Notifications plugin) to the new Cocoon configuration.

Screen Shot 2016-01-19 at 14.14.10


If the Notification plugins are installed the application is ready to be compiled. Before compiling an APK or a Developer app check your integration in the following step.


Local Notifications

This plugins doesn’t need any parameters.

Parse Push Notifications

The Parse Push Notifications plugin requires an APP_ID and CLIENT_KEY parameters in the new cloud. These parameters should have been automatically set during the migration process but just in case check that is the same as the on in the old CocoonJS cloud.

Screen Shot 2016-01-19 at 14.12.11



The old CocoonJS Notifications plugins have been recoded in the the new Cocoon so the API is not exactly the same but we really think it is for good. We have tried to make a simpler and easier to integrate API so the changes in your application code shouldn’t be difficult to implement.

Check the Notifications plugins guides to see what modifications you should made in your code to get the new Cocoon Local Notifications Plugins and Parse Push Notifications plugins working:

local_button parse_button