Skip to content
Using Android Background Services in NativeScript
JavaScript CSS
Branch: master
Clone or download
Latest commit a90789a Jul 26, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
app test: fix e2e tests. Jul 26, 2019
e2e test: fix e2e tests. Jul 26, 2019
.gitignore tests: fix failing test May 6, 2019
README.md refactor: improved README and gitignore Jun 27, 2018
package.json chore: fix versioning Jul 16, 2019
webpack.config.js chore: update deps May 7, 2019

README.md

Notifications Scheduler

IMPORTANT: In order to use the custom com.pip3r4o.android.app.IntentService implementation, you need to install the nativescript-android-utils package as a plugin in your application.

Note:: This demo is using android.app.NotificationChannel which is available only for API 26+ (Android 8 and above).


To see an iOS version of this sample please check - https://github.com/NativeScript/sample-ios-background-execution

A sample project demonstrating how Android background services work in NativeScript, using the Android AlarmManager to schedule periodical calling of an IntentService, which should create Notifications even when the Application's Activities have been destroyed. (Caution: Be very mindful when developing applications which send out notifications. Some users may find them annoying, if they get them too often, and as a result - delete your application.)

Running the sample

    git clone https://github.com/NativeScript/sample-android-background-services
    cd sample-android-background-services
    tns run android

Notes

  • IntentService’s onHandleIntent will execute on the main UI thread (versus on a dedicated worker Thread when implemented in pure Android) IntentService’s implementation needs to use a constructor that takes no arguments, but that currently is not possible through Java.
  • The base Service class and all its descendants execute on the main UI thread by default in Android. Implementing a service that should run on a background thread must be managed in Java by the developer (see Notes).
  • BroadcastReceivers should not be registered with the android: process =":remote" property in the AndroidManifest as the receiver will be unable to execute JavaScript in an independent process
  • The suggested approach when you want to offload a long-running job on a different Thread is to write the implementation in Java classes and invoke the job in NativeScript.
  • The current implementation utilizes the NotificationChannel, which was added in API Level 26. If you want to target lower API Levels, take a look at the older implementation Alarm Manager Implementation. Have in mind, that this approaches is not supported with API Level 26 or newer due to limitations in the OS.
You can’t perform that action at this time.