-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CleverTap not invoking notification #146
Comments
@rahul-chefkart Can you provide clevertap logs using |
@piyush-kukadiya From where I can find the clever tap logs Can you please suggest? I have set the debugging using setDebugLevel in my app. |
@rahul-chefkart From Android studio logcat |
@piyush-kukadiya Please check the logs given below - V/Capacitor/PushNotificationsPlugin: Notifying listeners for event pushNotificationReceived To native (Cordova plugin): callbackId: INVALID, service: CleverTapPlugin, action: createNotification, actionArgs: [{"id":"0:1653455898990116%bcd1f0abf9fd7ecd","data":{"wzrk_acct_id":"TEST-XXXXXX","nm":"test","nt":"Test","wzrk_pivot":"wzrk_default","wzrk_cid":"test","wzrk_rnv":"false","wzrk_ttl":"1653542295","wzrk_push_amp":"false","wzrk_bc":"","wzrk_bi":"2","wzrk_ck":"1455895960","wzrk_dt":"FIREBASE","wzrk_id":"0_0","wzrk_pn":"true"}}] Also, there is no clevertap listener that I have added in the service file. |
Hi Folks,
I have implemented the CleverTap service in my ionic capacitor project.
List of dependencies and version of packages are as follows:
"@ionic-native/clevertap": "^5.36.0",
"@capacitor/local-notifications": "^1.0.8",
Techs Used:
Ionic 5
Capacitor 3
Reactjs
Also added the metadata to the Android manifest file.
Issue - When invoking a push notification from the CleverTap dashboard and handling it using the "@capacitor/local-notifications" it is visible on the notification tray but whenever I call the CleverTap.createNotification(data) the notification is not getting reflected on the tray.
All the configuration and implementation are the equals documentation.
The text was updated successfully, but these errors were encountered: