Distribution delay when changing In-app Price and product description in the Google Play Developer Console

Question

How long does a price / description change usually take place in the Google Play Developer Console to take effect and distribute to devices?

I have two In-App products that I am testing with price and description changes.

Using getSkuDetails() from the IabHelper library, I can request this information while the application is running. After changing the information in the Google Play Developer Console, a change in description was found quite quickly in the application. However, it was 2 hours, and the price change has not yet requested updated information - it still receives the original price.

Given that I changed both parameters at the same time, I expected both to have the same propagation delay.

What raises a new question: if the delay is significant, what happens during this interim period? Has the price been changed for purchases so that when viewing the Google Wallet workflow, the new price will be displayed, but the value shown to customers in the application received through getSkuDetails() will reflect the original price?

I looked through the documentation, but there is very little information about what happens when prices change. This blog post was helpful at a high level:

http://android-developers.blogspot.ca/2012/12/in-app-billing-version-3.html

Answer 1

Today I had a similar problem, which turned out to be a mistake in the way I changed the Prices. I am based in the UK and change the default price field from 1 GBP to 30 GBP.

The application is not yet live, so I did not change the local prices beyond the page, which meant that the store was returning the local price for the UK, which was still the original 1 GBP.

I had to check the option “Overwrite existing prices” and click the “Automatically convert prices now” button, and finally I had to save the product before it returned the correct price. It was still not immediately updated, but ultimately returned the correct price after about 3 hours.

Answer 2

I believe that this should happen instantly if everything is done correctly. If this is not the case, then this is not a problem for stackoverflow, but rather for Google. I would advise you to contact support.

Sorry for the short answer = /

Answer 3

I watched the same behavior. Clearing the cache in the Google Play Store app fixed this for me.

Just forcibly stopping my application or the Google Play Store no. There was also no cache clearing in either my application or the Google Play Services.