Trevor,
Thank you for your prompt response and the explanation. At least now we
know that we are not living in some alternate reality and stopped pinching
ourselves in disbelief.
But, we still have all of our customers subscriptions canceled. None of
those were restored back to active. Now when we query the Google API server
to see if the subscriptions are still active we get "false".
For example:
We queried Google order number: 574480490664998 and got the following JSON
response:
{
"kind": "androidpublisher#subscriptionPurchase",
"initiationTimestampMsec": "1342064134000",
"validUntilTimestampMsec": "1344749703290",
"autoRenewing": false
}
That order should have been restored to autoRenewing: true!
Please let me know if we are missing something?
Our customers have not had any termination of service, since our servers
are correctly keeping track of the expiration date of their subscriptions.
But that is not the point. The main thing is that they would have to now
manually go and purchase the same subscription they did subscribe to before
(the one they did not unsubscribe from).
I think that is a horrible way to treat them.
I do not want to sound harsh, but we are trying to run a business not
play high school games.
Any help is greatly appreciated!
Thank you.
On Thursday, 9 August 2012 21:29:30 UTC-4, Trevor Johns wrote:
>
> fibercode,
> A number of in-app billing subscriptions were erroneously marked as
> canceled this morning due to an issue on our servers. Most of the affected
> subscriptions have already been restored by our engineers, and users did
> not loose access to content during this time. We will be sending a followup
> email soon to those affected explaining what happened.
>
> There were a small minority of users who's subscription auto-renewal dates
> occurred before we we were able to restore the subscription, and
> accordingly were not renewed. These users can choose to re-subscribe using
> the standard in-app billing mechanism within your app (they will appear as
> a standard expired subscription to your app).
>
> The HTTP Android Developer API would have still returned the correct
> expiration time for all subscriptions, so users continued to receive all
> content they had paid for.
>
> We sincerely apologize the inconvenience this has caused, and our team
> will be taking steps to ensure similar incidents do not occur in the future.
>
> --
> Trevor Johns
> Google Developer Programs, Android
> http://developer.android.com
>
> On Thursday, August 9, 2012 12:03:23 PM UTC-7, fibercode wrote:
>>
>> One of our Android applications has supported in app billing for a while
>> now.
>>
>> A little over two weeks ago we published an update that supports the
>> newly released by Google in app subscriptions.
>>
>> Everything was fine until this morning when mysteriously all the
>> subscriptions purchased by our customers were canceled automatically!!!!!
>> We got up this morning, checked our emails and our test accounts had the
>> subscriptions canceled even though we had not done that. This obviously
>> raised a lot of red flags so we started checking our customers'
>> subscriptions and it seems that they were all canceled !!! We were even
>> contacted by several of our customers who thought that we canceled their
>> subscriptions.
>>
>> The new subscription purchases done today (August 9th) are not being
>> canceled but we can no longer trust how long that will last.
>>
>> The only conclusion we could come to is that Google canceled the
>> subscriptions (either on purpose or accidentally).
>> Most likely this looks like a bug on the Google side, but we need some
>> help to narrow this down.
>>
>> Thank you.
>>
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
