I had the same issue - some failed attempts because of network issue on Beeblex end. It occurred to me a workaround - when Beeblex is failing simply accept the receipt without validation. That's what I'm going to program for my next update... seems like a simple solution, a workaround. I have in fact already caught 6 Beeblex hack attempts (I'm measuring the events in Flurry). So yes, it is useful. And yes, sometimes Beeblex has issues. But at least in my case, the hacks amount to so very little anyways, at least where I am now, that bypassing the security review is not a problem. If I miss a few validations, oh well.
On Friday, May 10, 2013 1:56:11 AM UTC-7, Nguyễn Minh Tuấn wrote: