Hello ,
Thank you for your feedback. We have fixed that plugin dynamic path issue. You can download the new version of our plugin and check.
– Please make sure that you will add android gcm/fcm key and ios certificate properly from add setting page.
The os_type and device_token parameters need to be passed as Request headers in your login API, as well as in your register and update use API.
You can check the below link for how to pass the parameters in request headers from android app.
https://code.tutsplus.com/tutorials/http-headers-for-dummies–net-8039
https://stackoverflow.com/questions/16793647/how-to-set-request-header-for-sending-data-from-android-apps-to-our-server
When android developer call for login API, register API and update user API for your Application, He/She must pass the os_type and device_token parameters in API request headers always. As because the user’s device token may vary as per his mobile devices .
Once you passed those request headers in your API you can then check in your database that in ‘all_pushnotification_token’ Table the device token and os type has automatically inserted.
Example:
os_type=’android’
device_token=’abcd123456′
-If you are using the plugin and found it to be useful in your projects, We would urge you to give us rating and review, it will help us making plugin more effective with future releases.