http://blog.parse.com/?mkt_tok=3RkMMJWWfF9wsRonv6rPZKXonjHpfsX56uQtWaezlMI%2F0ER3fOvrPUfGjI4ARMNiI%2BSLDwEYGJlv6SgFTbHGMblmy7gNUxU%3D Cheers! -- Smug

Wow.. that is huge news :/

Since this is only Push notification that works for me, it would be fine if somebody make BT notifications to work without any problem. I wait for this more than a year, but nothing changes.

If Parse was never bought by FB, I wonder if it would still be humming along. Good point Miku -

And that's why I wonder if anyone is capable to finnaly solve problem of push notifications on BT, apps without them have lesser chance.

I think it's the server you self hosting on that has problemsa. Not sure if is actually buzztouch. What problems were you having?

Chris, here: <a href="https://www.buzztouch.com/forum/thread.php?tid=71C4BBC09B68D8972AE23BE&command=isSearching&currentPage=2&topicTitle=&createdBy=miku&repliedBy=&minViews=-1&maxViews=-1&minReplies=-1&maxReplies=-1&forumCategory=" target="_blank" rel="nofollow">https://www.buzztouch.com/forum/thread.php?tid=71C4BBC09B68D8972AE23BE&command=isSearching&currentPage=2&topicTitle=&createdBy=miku&repliedBy=&minViews=-1&maxViews=-1&minReplies=-1&maxReplies=-1&forumCategory=</a> is the thread in which you adviced me to use Parse instead. And I did and I am happy that Parse work on both Android and iOS. Can you tell what server problems might be possible? I can easily contact my provider and make changes this to work. I checked my self-hosted server has these outbound ports open: 1. TCP port 5223 (used by devices to communicate to the APNs servers) 2. TCP port 2195 (used to send notifications to the APNs) 3. TCP port 2196 (used by the APNs feedback service) 4. TCP Port 443

At least parse will be releasing a self hosted server option, could be a good thing in the long run.

Unfortunately, the Parse Server does not support Push Notifications. From their page (near the bottom of the page): https://parse.com/docs/server/guide#migrating "Push Notifications Parse Server does not implement any push notification functionality. We recommend migrating to a different push provider. You can export all your data in your app settings and grab the device tokens in the Installation class and upload it to another push provider. Alternately, you can also grab these tokens directly from your MongoDB under the installations collection. You will then need to publish a new version of your app replacing Parse’s push registration with the other service."

Hi all, Disappointed about it, btw optional you can switch to CloudKit for ios apps too https://developer.apple.com/icloud/

Parse Alternatives https://github.com/relatedcode/ParseAlternatives?utm_source=andybargh-newsletter-20160202&utm_medium=email&utm_campaign=andybargh-newsletter

But why to search for alternatives, if PN is inside BT? Today I tried again to create PN inside BT. I have valid .p12 certificate which works fine in Parse. I translated it to .pem. Whatever I do, always I got message in panel: "There are no iOS Devices registered. You can't send messages until devices are registered. Devices need to register as "Live" or "Design", depending on which mode you selected." Can anybody tell why this is not working?

Did you choose to allow push in the app when it asked? That's what registers the devices. I'm going to play with this also later. Also what kind of server are you using. A cheap shared server from a hosting provider might not be good enough. You might need something like a vps or dedicated server. Using the self hosted or even creating my own are my plans, so I don't have to deal with another service migration. Backendless looks pretty good too. Parse is recommending aws,etc, which parse was built on. I'm still going to stick with my own push service with bt or my own custom one.

In panel I have chosen to ask for PN, but when I start app, it doesn't ask. I think that server I use is gogod enough, I have plenty of Joomla sites installed, nothing went wrong so far. Ports: 1. TCP port 5223 (used by devices to communicate to the APNs servers) 2. TCP port 2195 (used to send notifications to the APNs) 3. TCP port 2196 (used by the APNs feedback service) 4. TCP Port 443 Parse works fine on iOS and Android.

https://mobile.awsblog.com/post/Tx3NE69QDHI7LJK/Migrating-from-Parse-Push-to-Amazon-SNS Parse of course has better servers. I wouldn't think it would be any ports, it would be the capacity of your server if your server was the problem. My shared hosted works fine though too. What are the errors do you get?

I asked my provider and server is in top condition, among fastest. I don't get error, but I got message in panel: "There are no iOS Devices registered. You can't send messages until devices are registered. Devices need to register as "Live" or "Design", depending on which mode you selected." Looks that BT doesn't recognise any device.

I spent weeks trying to get BT push notifications working without success. The guides were out of date and nothing seemed to work. I hope that this is something that is being fixed in the all new Buzztouch whenever it appears that is.

Only few weeks? I try whole year, no one has answer why this in NOT working.

Hi there option going back to Parse SDK ? I have good news, for all of you who loved Parse backend, I just wanted to let you know that we’ve found out a nice BaaS service which offers 1GB free and hosts a Parse Dashboard, it’s called back{4}app and allows you to use the Parse SDK. Enjoy! Site: http://back4app.com