@oracle/react-native-pushiomanager
Advanced tools
This module makes it easy to integrate your React Native based mobile app with the Responsys SDK.
Before installing the plugin, you must setup your app to receive push notifications.
pushio_config.json file generated from your credentials and place it in your project's android/app/src/main/assets folder. You might have to create the directory if it is not already present.pushio_config.json file generated from your credentials.PushIOManager.xcframework and place it in YOUR_APP_DIR/ios/framework/ folder before adding plugin to project.The plugin can be installed with the React Native CLI,
cd <your_react_native_app>
yarn add @oracle/react-native-pushiomanager
Create a new directory - PushIOManager inside your app's android directory.
Download the SDK native binary from here and place the .aar file in this android/PushIOManager/ directory.
Inside the android/PushIOManager directory, create a file build.gradle with the following code:
configurations.maybeCreate("default")
artifacts.add("default", file('PushIOManager-6.56.3.aar'))
Add the following to your project-wide settings.gradle file:
include ':PushIOManager'
project(':PushIOManager').projectDir = new File(rootProject.projectDir, './PushIOManager')
After installing plugin you need to install cocoapods,
Go to ios directory of you app, cd YOUR_APP_DIR/ios/
Run pod install
Note: This step will fail if PushIOManager.xcframework is not available in YOUR_APP_DIR/ios/framework/ folder before adding plugin to project with npm or yarn. Copy the PushIOManager.xcframework to YOUR_APP_DIR/ios/framework/ and perform Installation step again.
Open the build.gradle file located in android/app/ and add the following dependency,
implementation 'androidx.core:core:1.6.0'
implementation 'com.google.firebase:firebase-messaging:17.3.0'
Open the AndroidManifest.xml file located in android/app/src/main and add the following,
Permissions above the <application> tag,
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="${applicationId}.permission.PUSHIO_MESSAGE" />
<uses-permission android:name="${applicationId}.permission.RSYS_SHOW_IAM" />
<permission android:name=".permission.PUSHIO_MESSAGE" android:protectionLevel="signature" />
<permission android:name="${applicationId}.permission.RSYS_SHOW_IAM" android:protectionLevel="signature" />
Intent-filter for launching app when the user taps on a push notification. Add it inside the <activity> tag of MainActivity,
<intent-filter>
<action android:name="${applicationId}.NOTIFICATIONPRESSED" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
Add the following code inside <application> tag,
<receiver android:enabled="true" android:exported="false" android:name="com.pushio.manager.PushIOUriReceiver">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<data android:scheme="@string/uri_identifier" />
</intent-filter>
</receiver>
<activity android:name="com.pushio.manager.iam.ui.PushIOMessageViewActivity" android:permission="${applicationId}.permission.SHOW_IAM" android:theme="@android:style/Theme.Translucent.NoTitleBar">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE" />
<category android:name="android.intent.category.DEFAULT" />
<data android:scheme="@string/uri_identifier" />
</intent-filter>
</activity>
(Optional) Intent-filter for Android App Links setup. Add it inside the <activity> tag of MainActivity,
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:host="@string/app_links_url_host" android:pathPrefix="/pub/acc" android:scheme="https" />
</intent-filter>
Open the strings.xml file located at android/app/src/main/res/values and add the following properties,
Custom URI scheme for displaying In-App Messages and Rich Push content,
<string name="uri_identifier">pio-YOUR_API_KEY</string>
You can find the API key in the pushio_config.json that was placed in android/app/src/main/assets earlier during setup.
(Optional) If you added the <intent-filter> for Android App Links in the steps above, then you will need to declare the domain name,
<string name="app_links_url_host">YOUR_ANDROID_APP_LINKS_DOMAIN</string>
Open the Xcode project workspace in your ios directory of cordova app.
Drag and Drop your pushio_config.json in Xcode project.
Select the root project and Under Capabilites add the "Push Notifications" and "Background Modes".
Add below Import statements in AppDelegate.h.
#import <PushIOManager/PushIOManager.h>
#import <UserNotifications/UserNotifications.h>
AppDelegate.h ,@interface AppDelegate : UIResponder <UIApplicationDelegate,UNUserNotificationCenterDelegate>
AppDelegate.m.- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:
(NSData *)deviceToken
{
[[PushIOManager sharedInstance] didRegisterForRemoteNotificationsWithDeviceToken:deviceToken];
}
- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
[[PushIOManager sharedInstance] didFailToRegisterForRemoteNotificationsWithError:error];
}
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
{
[[PushIOManager sharedInstance] didReceiveRemoteNotification:userInfo];
}
- (void)application:(UIApplication *)application didReceiveRemoteNotification:
(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler
{
[[PushIOManager sharedInstance] didReceiveRemoteNotification:userInfo
fetchCompletionResult:UIBackgroundFetchResultNewData fetchCompletionHandler:completionHandler];
}
//iOS 10 or later
-(void) userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:
(UNNotificationResponse *)response withCompletionHandler:(void(^)(void))completionHandler
{
[[PushIOManager sharedInstance] userNotificationCenter:center didReceiveNotificationResponse:response
withCompletionHandler:completionHandler];
}
-(void) userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:
(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler
{
[[PushIOManager sharedInstance] userNotificationCenter:center willPresentNotification:notification
withCompletionHandler:completionHandler];
}
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
[[PushIOManager sharedInstance] openURL:url options:options];
return YES;
}
For In-App Messages and Rich Push Content follow the below steps :
For Media Attachments you can follow the following guide. Copy and paste the code provided in guide in respective files.
For Carousel Push you can follow the following guide. Copy and paste the code provided in guide in respective files.
The module can be accessed in JS code as follows,
import PushIOManager from '@oracle/react-native-pushiomanager';
Configure the SDK,
PushIOManager.configure("your-pushio_config.json", (error, response) => {
});
Once the SDK is configured, register the app with Responsys,
import { Platform } from 'react-native';
if (Platform.OS === 'android') {
PushIOManager.registerApp(true, true, (error, response) => {
});
} else {
PushIOManager.registerForAllRemoteNotificationTypes((error, response) => {
PushIOManager.registerApp(true, (error, response) => {
});
});
}
```
Additional APIs (optional)
iOS Only:
// Implement before `registerForAllRemoteNotificationTypes` calls.
PushIOManager.setDelayRegistration(true);
Associate an app installation with a user (usually after login),
PushIOManager.registerUserId("userID");
When the user logs out,
PushIOManager.unregisterUserId();
User actions can be attributed to a push notification using,
PushIOManager.trackEngagement(3, properties, (error, response) => {
});
In-App Message (IAM) are displayed in a popup window via system-defined triggers like $ExplicitAppOpen or custom triggers. IAM that use system-defined triggers are displayed automatically.
IAM can also be displayed on-demand using custom triggers.
Your marketing team defines a custom trigger in Responsys system and shares the trigger-event name with you.
Marketer launches the campaign and the IAM is delivered to the device via push or pull mechanism (depending on your Responsys Account settings)
When you wish to display the IAM popup, use,
PushIOManager.trackEvent("custom_event_name", properties);
These below steps are required for iOS In-App Messages.
To Enable Custom URI scheme for displaying In-App Messages and Rich Push content follow the Step 1.
You can find the API key in the pushio_config.json that was placed in your Xcode project earlier during setup.
Follow Step 2 to add the required capabilites in your Xcode project for In-App messages.
Each Message Center message now supports an additional property called custom key-value pairs, it is a variable sized object with key value pairs and can be accessed like any other property of that message.
```javascript
PushIOManager.fetchMessagesForMessageCenter(messageCenterName, (error, response) => {
if(error == null) {
for(message of response.messages){
console.log(message.messageID)
console.log(message.message)
console.log(message.customKeyValuePairs)
}
}
});
```
If any message has a rich-content (HTML) then call,
PushIOManager.fetchRichContentForMessage(messageID, (error, response) => {
// 'response' is the HTML content
});
Remember to store these messages, since the SDK cache is purgeable.
Add the following messageCenter listeners to get notified when messages are available.
If your app uses React Class components, use lifecycle methods componentDidMount and componentWillUnmount to store and clean up the listener.
componentDidMount() {
this.messageCenterListener = PushIOManager.addMessageCenterUpdateListener((response) =>
console.log(response);
);
}
componentWillUnmount() {
if (this.messageCenterListener) {
this.messageCenterListener.remove();
}
}
If your app uses Functional components, update the useEffect hook to store the listener
useEffect(() => {
const messageCenterListener = PushIOManager.addMessageCenterUpdateListener((response) =>
console.log(response);
);
return () => {
messageCenterListener.remove()
}; };
If your app is setup to monitor geofence and beacons, you can use the following APIs to record in Responsys when a user enters/exits a geofence/beacon zone.
PushIOManager.onGeoRegionEntered(geoRegion, (error, response) => {});
PushIOManager.onGeoRegionExited(geoRegion, (error, response) => {});
PushIOManager.onBeaconRegionEntered(beaconRegion, (error, response) => {});
PushIOManager.onBeaconRegionExited(beaconRegion, (error, response) => {});
Preferences are used to record user-choices for push notifications. The preferences should be pre-defined in Responsys before being used in your app.
Declare the preference beforehand in the app,
PushIOManager.declarePreference(key, label, preferenceType, (error, response) => {
});
Once a preference is declared successfully, you may save the preference using,
PushIOManager.setPreference(key, value, (error, success) => {
});
Do not use this as a persistent (key/value) store since this data is purgeable.
Responsys SDK uses the app icon as the icon for notifications. You can change this by using the following two APIs,
PushIOManager.setNotificationLargeIcon("ic_notification_large");
PushIOManager.setNotificationSmallIcon("ic_notification_small");
drawable or mipmap directory, i.e. android/app/src/main/res/drawable or android/app/src/main/res/mipmap.It is also possible to change the notification small icon color by using the following API,
PushIOManager.setNotificationSmallIconColor("#d1350f");
With release 6.52.1, you can now subscribe to FCM device tokens and push notifications callbacks from the Responsys plugin.
PushIOManager.onPushTokenReceived( response => {
console.log("Device Token: " + response.deviceToken);
});
PushIOManager.onPushNotificationReceived( remoteMessage => {
console.log("Push Message: " + JSON.stringify(remoteMessage));
PushIOManager.isResponsysPush(remoteMessage, (error, response) => {
if (response) {
console.log("Received Push Message from Responsys");
PushIOManager.handleMessage(remoteMessage);
} else {
// Not a Responsys Push, handle it appropriately
}
});
});
This will allow you to handle push notifications while the app is in foreground or background.
These callbacks are also useful if you have multiple push plugins and need to decide how to process the incoming push notifications.
NOTE: When the app is in killed state (i.e. not in memory) the Responsys plugin will automatically process and display the push notifications.
When the user taps on a push notification (having a deeplink), the plugin passes the deeplink to the app.
Your app must implement the following native code to handle deeplinks.
Ensure that you have implemented openURL method in your AppDelegate.m, as follows,
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
[[PushIOManager sharedInstance] openURL:url options:options];
return YES;
}
In AndroidManifest.xml, change the launchMode of MainActivity to singleTask and add the following Intent-filter,
<activity
android:name=".MainActivity"
android:launchMode="singleTask">
<intent-filter>
<action android:name="${applicationId}.intent.action.PROCESS_RSYS_DEEPLINK" />
<category android:name="android.intent.category.DEFAULT" />
<data android:scheme="YOUR_CUSTOM_URL_SCHEME" />
</intent-filter>
</activity>
Add the following code to your MainActivity,
import com.facebook.react.ReactInstanceManager;
import com.facebook.react.bridge.ReactContext;
import com.facebook.react.modules.core.DeviceEventManagerModule;
import android.content.Intent;
import android.net.Uri;
@Override
protected void onCreate(Bundle savedInstanceState){
super.onCreate(savedInstanceState);
handleIntent(getIntent());
}
@Override
public void onNewIntent(Intent intent) {
super.onNewIntent(intent);
handleIntent(intent);
}
private void handleIntent(Intent intent){
if(intent != null && intent.getData() != null) {
final Uri deepLinkURL = intent.getData();
ReactInstanceManager reactInstanceManager = getReactNativeHost().getReactInstanceManager();
ReactContext reactContext = reactInstanceManager.getCurrentReactContext();
if(reactContext != null) {
reactContext.getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class).emit("PIOHandleOpenURL", deepLinkURL.toString());
} else {
reactInstanceManager.addReactInstanceEventListener(new ReactInstanceManager.ReactInstanceEventListener() {
@Override
public void onReactContextInitialized(ReactContext context) {
context.getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class).emit("PIOHandleOpenURL", deepLinkURL.toString());
reactInstanceManager.removeReactInstanceEventListener(this);
}
});
}
}
}
In your Javascript code, add the following deeplink listeners,
If your app uses React Class components, use lifecycle methods componentDidMount and componentWillUnmount to store and clean up the listener.
componentDidMount() {
this.deepLinkListener = PushIOManager.setOpenURLListener(true, deeplink =>
console.log("Deeplink: " + deeplink);
);
}
componentWillUnmount() {
if (this.deepLinkListener) {
this.deepLinkListener.remove();
}
}
If your app uses Functional components, update the useEffect hook to store listener
useEffect(() => {
const deepLinkListener = PushIOManager.setOpenURLListener(true, deeplink =>{
console.log("Deeplink: " + deeplink);
});
return () => {
deepLinkListener.remove()
};
});
If your app uses Functional components, update the react-natigation hook to store listener
const [isReady, setIsReady] = useState(false);
const config = {
initialRouteName: "Home",
screens: {
Home: {
path: "home",
}
}
};
const linking = {
prefixes: ["example://"],
config: config.
}
let deeplinkurl
const onReceivePushIOURL = (deeplink) => {
if (Platform.OS === "ios") {
deeplinkurl = deeplink.url;
} else {
deeplinkurl = deeplink;
}
console.log("onReceivePushIOURL deeplink: " + deeplinkurl);
if (deeplinkurl && navigationRef.isReady) {
Linking.openURL(deeplinkurl);
}
};
useEffect(() => {
const deepLinkListener = PushIOManager.setOpenURLListener(true, onReceivePushIOURL);
return () => {
deepLinkListener.remove();
};
},[]);
return (
<NavigationContainer ref={navigationRef} onReady={onNavigationReady} linking={linking}
)
Responsys plugin version 6.48.0 and above supports reporting Revenue/Purchase events. These events attribute purchases to the push campaign that led the app user into the mobile app. This API accepts an event object which allows In-App Purchase (Digital Goods) or Retail Purchase (Physical Goods) conversion-type to be reported.
var event = {};
event['orderId'] = '1234';
event['orderTotal'] = 50;
event['orderQuantity'] = 5;
event['conversionType'] = 3; // Possible values: 3 = In-App Purchase, 7 = Retail Purchase
event['customProperties'] = {}; // optional
PushIOManager.trackConversionEvent(event, (error, response) => {
});
With this release, we have made changes to our Multiple SDK guide after reports of duplicate notifications displayed due to a bug in @react-native-firebase/messaging plugin.
Make sure you review the updated guide as you upgrade the app to v6.56.3.
If you have been following our Multiple SDK guide, there are some changes with this release.
We no longer need the @react-native-firebase/app and @react-native-firebase/messaging plugins for multiple push plugin scenarios or to receive push in the background.
So, you may choose to uninstall these plugins.
yarn remove @react-native-firebase/app
yarn remove @react-native-firebase/messaging
With the release of v6.51.0, we have simplified the plugin integration process.
Due to this change, you will need to perform the following steps one-time only.
PushIOManager-6.50.1.aar file from app/src/main/libs directory.Find and remove the following line from the YOUR_APP_DIR/ios/Podfile,
pod 'PushIOManager', :path => '<PATH_TO_node_modules/@oracle/react-native-pushiomanager/PushIOManager/_Directory>'`
Create a framework directory inside YOUR_APP_DIR/ios/ directory.
Copy the latest PushIOManager.xcframework inside YOUR_APP_DIR/ios/framework/
Install the latest plugin yarn add @oracle/react-native-pushiomanager
If you have access to My Oracle Support, please raise a request here, otherwise open an issue in this repository.
This project welcomes contributions from the community. Before submitting a pull request, please review our contribution guide
Please consult the security guide for our responsible security vulnerability disclosure process
Copyright (c) 2024 Oracle and/or its affiliates and released under the Universal Permissive License (UPL), Version 1.0.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
FAQs
React Native Module for Responsys Mobile SDK
The npm package @oracle/react-native-pushiomanager receives a total of 511 weekly downloads. As such, @oracle/react-native-pushiomanager popularity was classified as not popular.
We found that @oracle/react-native-pushiomanager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware negotiators share how modern cybercriminals operate like corporations, using specialized teams, negotiation tactics, and reputation management.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.