Implement one signal player id to my backend database
Budget: $30 – $50 USD
Hello, i am using webview gold ios and android and i will like to implement native push notification for one signal in my app so when a user receives a message or any activity, it will show as pop up and indicate notification.
(My website is pure PHP, no framework)
one signal is already installed but the one signal player id needs to be installed in my backend This is the message they sent on how i can achieve this
So you might need a freelancer who does a little bit of back-end work to connect it to our OneSignal API: He/she should save the ?onesignal_push_id=XYZ parameter in a database, and fire the OneSignal API (https://documentation.onesignal.com/docs/onesignal-api) for that specific user as soon as a push notification should be sent. This has to be done by your back-end/webserver. WebViewGold only offers the built-in OneSignal API and the ability to deliver the ?onesignal_push_id=XYZ appendix to your WebView URL call.
iOS: Just activate the „kPushEnhanceUrl“ option in Config.swift (by switching the value from false to true) to append the individual user ID via ?onesignal_push_id=XYZ to your WebView URL.
Android: Just activate the „PUSH_ENHANCE_WEBVIEW_URL” option in Config.java (by switching the value from false to true) to append the individual ?onesignal_push_id=XYZ to your WebView URL.
If your WebView URL is https://www.example.org, WebViewGold will call https://www.example.org?onesignal_push_id=XYZ instead. Only your FIRST URL request will get that GET variable, so save it in a session or in a cookie to access it on your linked pages. An alternative or additional way would be to retrieve & process the information on any page via JavaScript:
<script>
window.location.href = "getonesignalplayerid://";
alert(onesignalplayerid);
</script>
(My website is pure PHP, no framework)
one signal is already installed but the one signal player id needs to be installed in my backend This is the message they sent on how i can achieve this
So you might need a freelancer who does a little bit of back-end work to connect it to our OneSignal API: He/she should save the ?onesignal_push_id=XYZ parameter in a database, and fire the OneSignal API (https://documentation.onesignal.com/docs/onesignal-api) for that specific user as soon as a push notification should be sent. This has to be done by your back-end/webserver. WebViewGold only offers the built-in OneSignal API and the ability to deliver the ?onesignal_push_id=XYZ appendix to your WebView URL call.
iOS: Just activate the „kPushEnhanceUrl“ option in Config.swift (by switching the value from false to true) to append the individual user ID via ?onesignal_push_id=XYZ to your WebView URL.
Android: Just activate the „PUSH_ENHANCE_WEBVIEW_URL” option in Config.java (by switching the value from false to true) to append the individual ?onesignal_push_id=XYZ to your WebView URL.
If your WebView URL is https://www.example.org, WebViewGold will call https://www.example.org?onesignal_push_id=XYZ instead. Only your FIRST URL request will get that GET variable, so save it in a session or in a cookie to access it on your linked pages. An alternative or additional way would be to retrieve & process the information on any page via JavaScript:
<script>
window.location.href = "getonesignalplayerid://";
alert(onesignalplayerid);
</script>