Hello,

I have developed a social iOS app with standard Like and Comment activities.

Push triggers (BL Scripts) were working as expected and iOS users got push notifications until a couple of days ago.

At the moment Users do not receive any push when triggered from Business Logic scripts. They DO receive if sent from console.

Issue seems similar to this one.

Any ideas?

Cheers,

Aris

It was an example of how it works and it should not. But today the situation is a little better. I noticed that messaging sometimes works sometimes not.  It seems to me that this service is not reliable for production. I wonder if it is the same situation when you take a paid package or it works 100%.

This code  does not work. No messages on phones.

function onRequest(request, response, modules) {

var push = modules.push;

push.broadcastMessage('message');

response.complete(200);

}

I do not believe that there is a simpler example.

I just did it on another account and it does not log the request. Either from the "Test" button in the code editor, or from the api console. I get a "success" and http status 200, but no logs.

I believe this is proof custom endpoints were affected aswell in the latest business logic version.

Please advise.

thx!

George

Good afternoon Aris,

My sincere apologies for the challenges you've experienced recently with the Kinvey service -- I'm sure these challenges have been very frustrating.  We take the quality and reliability of our service extremely seriously and certainly never intend for any user to experience this degree of difficulty with our platform.  We're working hard to correct the issues you've experienced and appreciate your forbearance.

Given the challenges you've experienced, I want to make sure that you get unblocked as soon as possible.  Where (if) you are still experiencing issues (with push notifications or anything else), can you please send us a copy of the business logic and the device token you're targeting?  This will enable us to do some additional internal testing specifically on your use case to ensure that your code is working as intended.

Apologies again for the difficulties -- we remain committed to turning this around for you.

Thank you for posting this Gary, this is something that we hadn't considered before now that we are looking into as a possible cause for push not working properly.

Guys push notifications are not working AGAIN! This is turning to a charade! 

If you can’t ensure that push notification or business logic scripts can run properly on your platform for at least 5 days in row, then you should be transparent and warn people prior to signing up with your service that you are facing major stability issues. 

In the event a key component was not working at Parse or any other tech company that respects itself, everybody would be running to resolve this issue. It is 2015, you are offering a BaaS and you can’t guarantee to your clients that push notifications will not stop working! 

Most important of all, you have companies that decided to invest their resources on Kinvey by building products on it and you are completely unable to run a proper service.

Br,

George

Aris, can you comment with a somewhat exact time as to when this started happening?

Also, can you please provide me with the KID of your app?

Thanks,

I have the same problem. This code doesn't work. If I put response.continue instead of response.complete i receive message on phone but got error 500 BLTimeOut. Please help.

function onRequest(request, response, modules) {

var push = modules.push,collectionAccess = modules.collectionAccess;

collectionAccess.collection('user').find({'username': 'beo.001'}, function (err, user) {

//push.broadcastMessage(user.username);

push.sendMessage(user, 'user.username');

});

response.continue();

}

Hello Damien,

I sent you my business logic script with email.

Cheers,

Aris

Thanks Aris, will review it now.

Thanks Aris / V3ga for the bug report.  

This is confirmed as a bug.  Single user push is *not* working in the latest version of business logic.   If you passed in an array of user(s)(1 or more) then your issue should be resolved.  

This should be addressed soon, though the workaround of passing a single user in an array will continue to work after the fix is implemented.

Thanks,