alert(data.aps.alert); This does not work at all
Here is my code that worked 4 hours ago
alert('Push Notification: ' + data.alert);
Apperyio("messageLabel").text(data.alert);
var currentPush = data.alert;
localStorage.setItem('pushNotification', currentPush);
Hello again,
So it seems that version 3.0 is working now , do we have to use data.alert or data.aps.alert ?
and Vinny did you try the ios version , does the push work as in android?
I can't get the app to run in xcode or ipa.. I have some errors. I think that appery has allot of backend stuff to fix so I ll have to wait. I'm surprised they push the last two updates without testing basic function.. I have no custom code... I guess this is all expected during an update.. It happened last time although it was not this bad but they did figure all the bugs out and appery was working great..the ability to import plugins is huge and worth the hassles.
still the same problem with version 3.0 , if we upgrade an existing app to v 3.0 , it won't register itself in the appery server devices database, please guys, you have to check it out, we can not rebuild our app from scratch in v 3.0.
Hello,
Please use codealert(data.message);/code now: https://devcenter.appery.io/documenta...
Hi Evgene , am not talking about the push itself, am talking about the application itself, when you install it on android, you won't find the device ID in the database, same app downgrade it to v 2.2 install it , it will register the device ID in the appery database, it seems there is a bug in upgrading an existing application already created in version less than 3.0 to version 3.0, if I was not very clear please rely I will back up my reply with images and more explanation.
Another thing, I did create a temp application, with same settings of google developer settings for push service and it worked , but I realized that device ID has changed in V 3.0, does it mean when you fix the issues in V 3.0 , users won't be able to receive pushes unless they run the application at least one time so to update the device ID , any idea about that ?
In version 3.0 the device id has become under the following format:
dxxxxxxxxxxxxxxa
while in prior versions, the device id was under the following format
3xxxxxxxxxxxxx5;dxxxxxxxxxxxxxxa
it is missing the first strings prior to the semi-colon including the semi-colon
Please take it into consideration.
Voltaire,
Please share your app that doesn't work for libraries 3.0 with support and tell us its name.
I just shared my app with support, its name: info-school-nab
Must mention that all my apps are having the same problem, but this one is a testing one, so in case you figured out the problem, I hope I can fix them all.
Thanks in advance