i update purchases_flutter 9.0.0 in google play show App must use Google Play Billing Library version 7.0.0

Hey ​@teekhawat-skunsubthara-aa804b, 

Thank you for reaching out. I’ll be happy to help!

If you updated the SDK to version 9.0.0, you’re now using version 8 of Google Play Billing Library. You need to upload a new version of your app to the tracks you actively publish to, so that Google can detect the library update for your app. After the app is approved by Google, the warning should not appear anymore. 

I hope this helps. Please let me know if you have any other questions!

I found Revenuecat new version SDK 9.0.0 can not restore purchase by user. so I downgrade to 8.20

Hey ​@hanks-10bbd3, 

Are you perhaps using anonymous users and expired transactions or consumed one-time products when trying to restore purchases? 

There is a limitation in Billing Library 8, which our SDK v9 integrates:

Play Billing Library 8 removed the ability to query for expired subscriptions and consumed one-time products. This means that the RevenueCat SDK will no longer be able to send purchase information from these purchases. There are 2 cases where this can have an impact:

• If you have consumed one time purchases in Google Play that need to be restored (for example, in order to grant a lifetime entitlement). In these cases, the SDK will not be able to find these purchases and will not be able to restore them and grant the entitlements. This can especially be a problem if you're using anonymous ids and don't have your own account system. Please make sure your products are correctly configured as non-consumables in the RevenueCat dashboard to avoid consuming them in the first place if you intend to make them behave as lifetime purchases.
• (Only relevant if you recently integrated RevenueCat before upgrading to v9, and do not (yet) have all your transactions imported). The SDK will not be able to send purchase information from these expired subscriptions and consumed one time purchases to our backend, so we might miss this data in our customer profile/targeting. We can still ingest historical data from these purchases through a backend historical import. See docs. This case doesn't affect developers that have all transactions in RevenueCat, which is true for the vast majority.

Please check the release notes here. 

If this is your case, your best option right now is to downgrade to an SDK version v8, which uses Billing Library 7, as you already did.

If this is not your case and you're still having issues, please let me know which types of subscriptions you're trying to restore and more details about your projects to troubleshoot further.