I really got into buzz touch and fell in love with the community but I am realizing that BT doesn't work with push notifications as far as I can tell. Can anyone get them working in BT 3? Please reply even if to say yes they work for you. I am SUPER BUMMED about this. I love BT but the most important feature for my app is push notifications. Is there a solution that includes staying with BT? I assumed it was me but after some research, I'm realizing its common. My issue is neither BT control panel can accept .pem files. I guess I would like some reassurance at this point. thanks

I have it working, works well. The posted instructions have one error that will prevent it from working... The key needed to enter in your control panel is a "Key for server applications", not specified in the instructions. Easy fix: 1. Go back to your Google Developers Console ---> APIs and Auth ---> Credentials 2. Under Public API Access hit "Create New Key". 3. Select "Server Key" 4. Leave the resulting box blank 5. Hit "Create" (this will create a key that will say "Any IP allowed.) 6. Put that new API Key in your control panel under GCM API Key 7. Put the Project Number from the overview tab in your control panel under GCM Project Number. 8. Save. -Tim

.PEM fix: In BT-server/bt_v15/bt_app change line 431 of file: bt_pushNotifications.php <<OLD>> //if(strtolower($userfile_type) != "application/octet-stream" || strtolower($file_ext) != "pem"){ <<NEW>> if(strtolower($userfile_type) != "application/x-x509-ca-cert" || strtolower($file_ext) != "pem"){ If you want to see how the old code was broken; I inserted this line to get visible output in the control panel that showed what the variables were set to. It was then apparent where the mismatch was: $strMessage = "<br/>file_ext is: " . $file_ext . " filename is: " . $filename . " userfile_type is: " . $userfile_type; -Tim

Those two errors effectively made push not work, one for iOS and one for Android. Tim

I tried that fix. Didn't work. I am only on iOS for now so I don't know about the android. I plan on waiting until I can get iOS working to attempt that. The fix doesn't work for my server side and I assumed you already changed it on the BT server side....which means the .pem issue would only be on the self server side but its on both. If I could get PN on the bt hosted apps I would just use it but I remade the app on both control panels and neither will accept any .pem's

That is the fix for self hosted. I have no control over the BT servers, I did tell them about the issue though.

just quadruple checked the bt server side to make sure I am not crazy and got: Invalid File Type. .pem files only. You tried to upload a file named Certificates.pem

thanks for your help. I actually thought you worked for them lol. You are a big help on here I even checked out your proposal example for the met app you made. Very interesting and helped with project timeline layout a lot! Unfortunately my control panel is still not accepting .pems

email me the certificate and i'll try to upload it on my server, maybe it's something with that. tim. at apps4ems.com Did you use p12pem.com to convert it or command line?

OMG I just reset safari and cleared cache and your fix worked. I don't know why I ever doubted you lol. Tim Wolf you are a patron and a saint!!!!

I'm neither. A Yankee and an Aggie, a weirder combination. Glad it worked. Tim

I only uploaded as dev but so far so good. Now I am doing all the cert stuff for distribution protocol. Its a big deal this approval thing. Making apps is fun. I was only planning on charging around 200 for an app until I started publishing with apple lol. Its a nightmare! Your app proposal plan helped me immensely. I never went to business school, just design and publication. Never thought I needed it. Boy was I wrong. Ya Im a Yankee as well. Born and raised. Hopefully my app biz takes off and I an make a Buzzcon someday. Ive seen posts of an east coast event. I would definitely make that! thanks again!