-
Notifications
You must be signed in to change notification settings - Fork 1
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Created pushHeadless sample app for push registration via headless on INSTALL vs on first launch. #9
Conversation
Does it only run on install? It would need to run every time the device boots as well would it not? |
Well technically the registration should only ever need to run once (on install) but yea the headless app should also run after each device boot :). |
@@ -0,0 +1,86 @@ | |||
# Push Headless Sample Application | |||
|
|||
The Push Headless sample push-enabled application demonstrates how to write a BlackBerry 10 WebWorks application that uses a backend headless service to register for push. This allows registration to be done on app install instead of on-first-run. The webworks portion will receive any pushes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Capitalization of WebWorks is incorrect
The native side should be reviewed by Shadid. Sorry, I don't know his GitHub user name. |
Still need to update WebWorks side to also read from config. |
Before merging this needs to have the changes from here ported https://github.com/blackberry/webworks-cli/pull/18/files |
BIS push passed for me. Getting steve to test as well. |
Rebased, Squashed. |
… INSTALL vs on first launch. -Includes WebWorks portion to receive and view pushes -Utilizes config.ini file for push credentials to avoid having to rebuild native component -Includes README for setup and information on how to send pushes for BES and BIS
Can somebody please merge this and get it into blackberry repo? |
Created pushHeadless sample app for push registration via headless on INSTALL vs on first launch.
No description provided.