Catch up wih the Appery.io community on our forum. Here you'll find information on the lastest questions and issues Appery.io developers are discussing.
https://forum.appery.io/
Hi Ihor, and happy new yr ! wish Appery.io success 
thks for your time on that matter. true, just realized that the webpage was changed and that the share function is different now.
has just set the toggle button to "on" share for both App and DB.
the App's name is o2o4pw,
and the DB's mybnoteDB.
best
Eric
Thanks for sharing. We'll test it. But unfortunately, it will take some time.
it's fine. I still hv a lot to do with other things to develop. just need iOS being able to receive notification some day I would be done with everything
thks a lot
Hi Eric -
Just to update the status, we reproduced behavior that you described us.
We will investigate what could be the reason of this.
thks for acknowledging.
looking forward to hearing from you with a good news,
Best!
Hi everyone!
Unfortunately I've come across the same issue working on my own app just now. That is on the iPhone I get the deviceID but not the token, I haven't tried android yet. I will try to solve this issue myself as well as jump aboard this conversation if anyone finds a solution.
Best regards,
Sebastian
Edit...
Forgot to mention these two tutorials on registration are slightly different. One say you have to add the request attributes: deviceID, token and type in body while the other one says query.
Hi Sebastian -
Could you please clarify what iOS version you're using for testing?
Also you can try to reconnect the DB in Push settings, rebuild the app and try installing on device once more.
Hello @EJLD!
Our developer tested your shared app backup and cloned DB and issue is not reproducible.
Looks like you've specified something wrong in iOS binary settings or Push settings. Please ensure you are using correct bundle id, certificates and provisioning profiles.
Hello @there!
your feedback is confusing
few days ago I received from your colleague:
xxxxxxxxxxxxxxxx extract of her msg xxxxxxxxxxxxxxxxxxx
EMPLOYEE
Illya Stepanov (Employee) 9 days ago
Hi Eric -
Just to update the status, we reproduced behavior that you described us.
We will investigate what could be the reason of this.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
when today you are coming back with something different.
strange service and communication to client
Hello!
Yes, but looks like Illya also specified some incorrect settings (we'll check it together with Illya and let you know result).
Based on Illya's report we created a bug and developer assigned to this bug can't reproduce it...
Please let me check with Illya his app, push settings, certificates, etc. I'll update!