Has anyone actually got push notifications on android working with BT 3.0?

Yes. Don't recall any real issues once I got the devices to register with my server.

I cant get devices to register The app just crashes when they say yes to accept push notifications

I remember that problem, I'm on the road but when I get back home later today I'll look back through some emails that I think have the fix. Don't remember what it was but think its simple. Tim

There was also a problem with some htc devices also, not sure if its been fixed or not.

Email me at: (translation needed below) tim.w at apps4ems.com I think there is a bug in the BT_gcmConfig.java when it's downloaded from the server, I'll send you one David fixed for me in October. You'll just have to change the package names and the GCM ID in the file. Tim

Would I too be able to have the fix? I have been having the same problem. Once I chose to register for PN, the apps closes. Thanks, Howard

Sure. I haven't heard from Chris if it fixed it for him yet.

@Tim, email sent thanks again, Howard

Hi @Tim, If you wouldn't mind I'd like to take a look too. 2.1.9 broke the android push on my self hosted server :( I'll email you too. TIA BTW It would be nice to have an "issue queue" or public list of known bugs ... just saying :) Cheers Darrel

I will have a look when I have some time over the next couple of days Thanks Tim Howard if you have any success let me know

@Tim, Thank you very much for all your help. I was able to register my device without the App crashing. Thank you again. @Chris. Yes it worked at was easy. Now I just have the problem that my phone notifies me of a message (sound and vibrate), when I send a notification, but I just can't see it on my phone. I have the "Show notifications" settings checked, so in theory I should be seeing them. Just another thing to look into! thanks again, Howard

Ok, I might have spoken to soon. I just tried testing it again. What seems to be happening is the notification is crashing the app... :-( If I have the app running in the background or actually up and running and send a notification, I get the message "unfortunately the app has stopped" Then closes the app. Any ideas? Howard

I havent got this file in my build anyway, so I'm clueless as to what to do

If you downloaded a 3.0 project for Android you should have that file in the src directory.

Got it thanks - will give it a try

Ok progress - well sort of .... Replaced the files and I can now register the device Succesfully send a push notification but nothing on the device

Hi Chris, I think we are in the same boat. Try this; Have your app open as if you were using it. Send a PN, and see if you get a message that it suddenly stopped and needs to close, or something like that. That is what is happening with me as of now. Thanks, Howard

Howard No what happens with me is that the push notification does not appear on device even though buzztouch says it is sent I guess the problem is with the Buzztouch Control Panel, but nobody from Buzztouch has answered if this is indeed the case or not

Ok, I guess my problem is half of that, because it does not show up either. So hopefully once that is fixed, and start showing up, I can work on why it crashes the app. Thanks for the update, Howard

Just been having a look at iOS push too Problem is guides are so out of date it's impossible In fact I believe it is impossible to set up push notifications with BT core 3.0 on Android or iOS. I havent found anyone yet who has anyway! I think I will give up - I've spent countless weeks on this to no avail My results: iOS - guides just don't make sense at all Android - done everything - registered devices but notifications don't appear on device

yea, its probably a small setting or error. Also I think it is lower on the list of priority for now! too bad. I really don't want to install a 3rd party PN, I want to keep the app simple. Will let you know if I hear of anything. Howard

I finally got somewhere with iOS but the buzztouch control panel won't upload my .pem file

Solved, probably: I was backtracking with a working app trying to figure what's different in the instructions posted on Buzz about Android Push and what I have implemented and I think I see the problem; 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. You should be good to go. Tim

Update: I did the above instructions. It registered my app without crashing. I sent a test message, the message appeared 3/4 of the way down, with the message the App "unfortunately has stooped". So it crashed it. But I did see the message for a split second. So I think we are getting there! :-) Thank you again for all your troubleshooting, Howard

Post or send me the crash report, I'll take a look. Tim

Where would I find that?

From the logcat in Eclipse if you're running it hooked to your computer, if it's live you should be able to get it from Google Play under crash reports.

I sent it to you via email. Thanks for taking the time, Howard

I have everything set up - my app no longer crashes on my device My device is registered to accept push notifications I send a notification from the buzztouch control panel and it says successfully sent - but it never appears on my device

Try using a server key instead of the way the instructions detail, a couple posts up...

OK used server key Progress - well sort of When app closed - send push notification - device announces it has received but nothing on screen With app open - notification appears on screen then app crashes

I believe that's the same problem Howard is having. Haven't solved that yet.

Did you guys ever figure this out....seems you have gotten farther than I have, I still get the "Problem communicating with Google Cloud Service" error. I am certain I have my API key, product number, etc all correct just cannot get device to register. My app is still in debugging mode (and all my API keys are signed with debugging keyfiles) just wondering if you guys are doing your testing in Live mode and maybe thats why I cannot get the device to register

Nope, I have not yet!

Well I actually found my issue but still no closer to a real working push....My issue was just a copy/paste error, when I pasted in my Google GCM Project Number to my manifest file there was a fantom letter "y" on the beginning of myGCM Project Number once i removed the "y", I no longer get the "Problem communicating with Google Cloud Service" message. Now my app just crashes when I try to accept the push acceptance dialog when the app first loads. I have tracked that down in logcat to what appears to be communications problem between my manifest file and BT_gcmConfig.java file. The Project Number is obviously an Integer stored in the manifest file but it looks like BT_gcmConfig.java around line 69 is looking for a string so I get this error: java.lang.Integer cannot be cast to java.lang.String

yea, I think that is where everyone is up to. Not sure if anything has figured out how to fix it.

If there was a modification for the BT_gcmConfig.java needed, could somebody please send it to me? I'm having app crashing issues as well. Thanks! Mark