How to disable OneSignal notification popup?
Is it possible to NOT show the popup notification of OneSignal and instead create one programmatically?

add a comment |
Is it possible to NOT show the popup notification of OneSignal and instead create one programmatically?

add a comment |
Is it possible to NOT show the popup notification of OneSignal and instead create one programmatically?

Is it possible to NOT show the popup notification of OneSignal and instead create one programmatically?


edited Nov 22 '18 at 1:04


jww
53.3k40230504
53.3k40230504
asked Nov 22 '18 at 0:15
PaoloPaolo
545
545
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Ok so after some research i found it out and is pretty straightforward.
here is the link to the offical doc on how to do it.
OneSignal Android Customizations
There are few step to achieve it:
1- Create a NotificationExtenderServiceClass
public class NotificationExtenderBareBonesExample extends NotificationExtenderService {
@Override
protected boolean onNotificationProcessing(OSNotificationReceivedResult receivedResult) {
// Read properties from result.
// Return true to stop the notification from displaying.
return true;
}
}
As you can see it's pretty clear, turning read to true will stop showing notifications.
But what the docs doesn't says is that FCM will stop working and instead the notifications will pass here.
2 - add the service to Manifest
<service
android:name=".NotificationExtenderBareBonesExample"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="false">
<intent-filter>
<action android:name="com.onesignal.NotificationExtender" />
</intent-filter>
</service>
That's it.
Now, adding your logic inside NotificationExtender you will be able to freely manage your notifications.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422215%2fhow-to-disable-onesignal-notification-popup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ok so after some research i found it out and is pretty straightforward.
here is the link to the offical doc on how to do it.
OneSignal Android Customizations
There are few step to achieve it:
1- Create a NotificationExtenderServiceClass
public class NotificationExtenderBareBonesExample extends NotificationExtenderService {
@Override
protected boolean onNotificationProcessing(OSNotificationReceivedResult receivedResult) {
// Read properties from result.
// Return true to stop the notification from displaying.
return true;
}
}
As you can see it's pretty clear, turning read to true will stop showing notifications.
But what the docs doesn't says is that FCM will stop working and instead the notifications will pass here.
2 - add the service to Manifest
<service
android:name=".NotificationExtenderBareBonesExample"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="false">
<intent-filter>
<action android:name="com.onesignal.NotificationExtender" />
</intent-filter>
</service>
That's it.
Now, adding your logic inside NotificationExtender you will be able to freely manage your notifications.
add a comment |
Ok so after some research i found it out and is pretty straightforward.
here is the link to the offical doc on how to do it.
OneSignal Android Customizations
There are few step to achieve it:
1- Create a NotificationExtenderServiceClass
public class NotificationExtenderBareBonesExample extends NotificationExtenderService {
@Override
protected boolean onNotificationProcessing(OSNotificationReceivedResult receivedResult) {
// Read properties from result.
// Return true to stop the notification from displaying.
return true;
}
}
As you can see it's pretty clear, turning read to true will stop showing notifications.
But what the docs doesn't says is that FCM will stop working and instead the notifications will pass here.
2 - add the service to Manifest
<service
android:name=".NotificationExtenderBareBonesExample"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="false">
<intent-filter>
<action android:name="com.onesignal.NotificationExtender" />
</intent-filter>
</service>
That's it.
Now, adding your logic inside NotificationExtender you will be able to freely manage your notifications.
add a comment |
Ok so after some research i found it out and is pretty straightforward.
here is the link to the offical doc on how to do it.
OneSignal Android Customizations
There are few step to achieve it:
1- Create a NotificationExtenderServiceClass
public class NotificationExtenderBareBonesExample extends NotificationExtenderService {
@Override
protected boolean onNotificationProcessing(OSNotificationReceivedResult receivedResult) {
// Read properties from result.
// Return true to stop the notification from displaying.
return true;
}
}
As you can see it's pretty clear, turning read to true will stop showing notifications.
But what the docs doesn't says is that FCM will stop working and instead the notifications will pass here.
2 - add the service to Manifest
<service
android:name=".NotificationExtenderBareBonesExample"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="false">
<intent-filter>
<action android:name="com.onesignal.NotificationExtender" />
</intent-filter>
</service>
That's it.
Now, adding your logic inside NotificationExtender you will be able to freely manage your notifications.
Ok so after some research i found it out and is pretty straightforward.
here is the link to the offical doc on how to do it.
OneSignal Android Customizations
There are few step to achieve it:
1- Create a NotificationExtenderServiceClass
public class NotificationExtenderBareBonesExample extends NotificationExtenderService {
@Override
protected boolean onNotificationProcessing(OSNotificationReceivedResult receivedResult) {
// Read properties from result.
// Return true to stop the notification from displaying.
return true;
}
}
As you can see it's pretty clear, turning read to true will stop showing notifications.
But what the docs doesn't says is that FCM will stop working and instead the notifications will pass here.
2 - add the service to Manifest
<service
android:name=".NotificationExtenderBareBonesExample"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="false">
<intent-filter>
<action android:name="com.onesignal.NotificationExtender" />
</intent-filter>
</service>
That's it.
Now, adding your logic inside NotificationExtender you will be able to freely manage your notifications.
edited Nov 23 '18 at 7:53
answered Nov 22 '18 at 1:02
PaoloPaolo
545
545
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422215%2fhow-to-disable-onesignal-notification-popup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown