wrong userdata notification on chrome

Comments

17 comments

  • Avatar
    Ivan Dedov

    Hello!

    It is a known issue. Due to the current implementation, Chrome Web Pushes still don't have any payload, and the only way to pass any content is to fetch the latest message from your Push History. At the moment, we can only "inform" your Chrome browser that there is a message available for it. The browser will go to our server and grab the latest message — please keep in mind that there is no way we can point it towards the specific message, hence there is a possibility that your browser will fetch the content of the different message.

    Our engineers are working on the new version of Web Push SDK and in the future this issue would be mended. Please follow our Blog for updates:

    https://www.pushwoosh.com/blog/

  • Avatar
    Ti

    The browser will go to our server and grab the latest message

    Well the current implementation can handle this by setting a flag when the message is requested/seen by some token, then you can send or not the message.

  • Avatar
    Ivan Dedov

    Yes, our engineers are working on the new SDK at the very moment. Stay tuned for updates in our Blog:

    https://www.pushwoosh.com/blog/

  • Avatar
    Ti

    Hi, we have updated to the last version (http://docs.pushwoosh.com/docs/web-sdk-20) and we stil getting the wrong notification.

    nodejs sample code

    var Pushwoosh = require("pushwoosh-client");
    
    var clientPW = new Pushwoosh("xxx", "xxx");
    
    var devices = ["dxnOg-x7Ghw:APA91bEhAealka8y9QiPsH8g8vjBcXwxMGZ818A8XOWhQORwRUu8TzsiRce1esIxJJa68K66o41NMAoKtJFCryZkW3dBmg-9jab0BYHz2cNFDo9OBX05VVvt96cyInFCcasRS2a1FQRM"];
    
    var options = {
        send_date: "now",
        ignore_user_timezone: true,
    
        devices: devices,
    
        platforms: [11]
    };
    
    clientPW.sendMessage("some random message", options, function (err, data) {
        console.info("send", err, data);
    });
    

    alt text

  • Avatar
    Subb Iah

    Hi, we have updated to the last version (http://docs.pushwoosh.com/docs/web-sdk-20) and we stil getting the wrong notification.kindly give your updates

  • Avatar
    Ti

    how hard is sending the current token to get the last message and flag it as delivery so i can get the correct notification data.


    the pushwoosh team does not event give attention to the this community, people here have no answers.


    the correct "message" should be "Sitemercado Loja Teste: Rafael, recebemos seu pedido para RETIRADA, assim que estiver pronto enviaremos uma mensagem de confirmação. Cod: E3848" the correct "push_id" data should be: "23933"

    check the images

    pushwoosh request

    pushwoosh result

    chrome console log

  • Avatar
    Ivan Dedov

    Please note that in the Web SDK 2.0 it is still not possible to send any payload, we are looking forward to following updates.

  • Avatar
    Ti

    Yes we know about that @idedov

    We know that pushwoosh request the api to grab the last message but it gets the wrong message.

    Just send the current pushtokenid to the api get the correct message and flag it as delivery, so it wont be delivered again, how hard is this?

  • Avatar
    Ivan Dedov

    @superainovacoes Please note that since api grabs the very last message it is not always possible to flag it since it could have been intended for the different platform.

    Still, the main reason for all the issues is that payload for Chrome requires encrypting. We continue to look into different solutions.

    Thank you for your patience and understanding.

  • Avatar
    Ti

    @idedov since the webpush notifications are easy to handle, you could change the service worker to send the current browser, chrome/firefox/safari then you can handle the last message based on for the web push not mobile, and flag it has been delivery for the specify token/browser.

    this is easy to do and easy to release a hot fix, seens to be a solution for the problem!

  • Avatar
    Ti

    @idedov status please?

    we really need some hurry on this

    we need to send a specific message to each user

    the solution without php encrypt i said above will work

    this will take 5min of pushwoosh team!

    send the pushtoken with the getlastmessage request filter it when it appear on the request and delivery the correct message using the pushtoken filter

  • Avatar
    Subb Iah

    @idedov kindly update your status

  • Avatar
    Ivan Dedov

    @superainovacoes @Subb Iah

    I am happy to inform you that we have implemented encryption and Chrome pushes can be sent with payload from now on! Please make sure that you have updated to our Web SDK 2.0

  • Avatar
    Subb Iah

    Thanks for your updates, now it is work fine

  • Avatar
    Ti

    thank you guys, it's working now!

  • Avatar
    Ti

    so now when i send something like this example:

    message: hi1 token: token1

    message: hi2 token: token2

    the correct message will be delivery for both clients? @idedov can you confirm this?

  • Avatar
    Ivan Dedov

    @superainovacoes yes, I can confirm. Correct message will be delivered for both.

Please sign in to leave a comment.