The watch-app crashes when it receives the data from the phone. No data is sent from the watch to the phone in our case and the Android app doesn't crash, as it seems to be the problem described in the link you mentioned.
I'm sorry that you are feeling the stress you are. No hard feelings. I am a little concerned by what you are reporting.
Are you on the 3.20.2 version?
The issue you mention about Integer not being parsed as a Number was specifically addressed and verified so if it has come back up or we have a gap in our verification I'd love to know ASAP so we can push things out. We've been working hard on trying to get a little faster turn-around on GCM and the GCM team has been really receptive to us. My hope is that this is a continued and growing trend.
I write to apologize for my report. There's no problem at all with the types. I spent a couple of hours building a CIQ app and an Android app to test how every type is parsed, and they are all OK. So I went back to my apps and I found that the crash was completely my fault. I have no idea why I only saw it happening after the GCM update. Most probably it was just a coincidence. I'm really sorry for blaming the wrong monkey.
I suggest that you delete this thread, as it may mislead other developers.
I think the only good thing I said was about launching BETA versions of the GCM. Is it really out of the question?
