Incorrect implementation of in-app billing (Android) - how to fix?

Hello,

I have just received a security alert from Google Play Store saying: Incorrect implementation of in-app billing.

I don't understand what this is, as far as I was aware my in-app purchases were working fine.  Google send me to this article:
*****
This information is intended for developers of apps that have a vulnerable implementation of in-app billing.

If your app is invoking the in-app billing service without setting a target package for the intent, this can enable a malicious package to bypass the Play Store's purchasing system and access data from your app.

Steps to fix:

If you are using IabHelper, please start using the latest SDK.
If you are manually invoking the in-app billing service, please ensure that you are calling Intent.setPackage(“com.android.vending”) on any intents to "com.android.vending.billing.InAppBillingService.BIND".
Sign in to your Developer Console and submit the updated version of your app.
Check back after five hours – we’ll show a warning message if the app hasn’t been updated correctly.
*****

But it doesn't mean anything to me - has anyone come across this before?

This sounds like something within Stencyl isn't upto the 'security standards' of Google Play, but I'm clueless in this so I could be very wrong. 

Thanks

So after pulling teeth from the Google Support contact member I think the case is....

...Google have discovered some security vulnerabilities across the board in the way in-app purchases are dealt with, and they're trying to close the loophole.  Unfortunately I think this may mean the code in Stencyl Engine being updated...

Maybe one of the team here knows more??

I also got this message today and have no idea right now what I can do to fix this?
So to the Stencyl developers; Can you read this thread and see if it makes any sense to you: http://stackoverflow.com/questions/38642622/google-play-warning-incorrect-implementation-of-google-play-inapp-billing

Thanks!

Also reported on the issue tracker here. This is something we'll need to update on our side, so we'll update the issue when that's done.

I also got this Warning message! How to fix this?

Hey Guys,

Yes, I'm getting this as well :S
Luckily I'm still in 'Closed Alpha' so it's not affecting me too much, but yeah, not sure if this has been fixed on Stencyls side yet?

The issue I linked to is marked as resolved. Do you have the latest version of Stencyl? If there are still problems, please update the issue and let us know.

http://community.stencyl.com/index.php?issue=440.0