Skip to main content
Question

Will the Old API Key Remain Supported? Migration Issues & Deprecation Concerns


Forum|alt.badge.img

I’m still using the old API key because when I tried migrating, purchases made with the old key weren’t recognized by the new API (I opened an issue here: https://github.com/RevenueCat/purchases-flutter/issues/472).

 

Today I tried migrating again and noticed the issue still persists. Subscriptions made with the old API key are recognized by the new API, but one-time purchases still aren’t.

 

If the user taps the “Restore Purchases” button, it does correctly recognize it — but I feel like that’s unnecessary friction for the user, and it could lead to negative feedback for the app.

 

I’m also getting the lint warning that Purchases.setup (Flutter) is deprecated. So I just want to know: can I still keep using the old API key? And will support for it eventually be dropped?

As a side note, when I restore the purchase made with the old API key, I get this message on console, and then the purchase is fully restored:
 

🤖‼️ Couldn't acknowledge purchase after restoring it, this most likely means the subscription has expired already or the product has already been acknowledged.
W/[Purchases] - WARN(16026): ⚠️ Unable to start a network connection due to a network configuration issue: https://api.revenuecat.com/v1/receipts
D/[Purchases] - DEBUG(16026): API request started: POST /receipts
D/[Purchases] - DEBUG(16026): API request completed with status: POST /receipts 400
E/[Purchases] - ERROR(16026): 😿‼️ PurchasesError(code=UnknownBackendError, underlyingErrorMessage=Backend Code: 7651 - The payment for this non-subscription product is not complete., message='There was an unknown backend error.')
D/[Purchases] - DEBUG(16026): 💰 Not consuming in-app purchase according to server configuration. This is expected for non-consumable products. The user won't be able to purchase this product again.
D/[Purchases] - DEBUG(16026): 💰 Acknowledging purchase with token badkbmipdehdfnclebclcjpf.AO-J1Owp8f5cvBztQwOGJdi20ifz_Euz1znlTUP5Qi79Q2bSnUsCEIjww1fqLMob31i-P0PJ3uR2Qfs-tcEk3Fdy5htnhsl6pfmFVZXbhJ0fAgPkalOjyULNn1bddcsEn_MV_egxiR4k
E/[Purchases] - ERROR(16026): 😿‼️ Error restoring purchase: StoreTransaction(orderId=null, productIds=[ga_basic_lifetime], type=INAPP, purchaseTime=1746651569660, purchaseToken=badkbmipdehdfnclebclcjpf.AO-J1Owp8f5cvBztQwOGJdi20ifz_Euz1znlTUP5Qi79Q2bSnUsCEIjww1fqLMob31i-P0PJ3uR2Qfs-tcEk3Fdy5htnhsl6pfmFVZXbhJ0fAgPkalOjyULNn1bddcsEn_MV_egxiR4k, purchaseState=UNSPECIFIED_STATE, isAutoRenewing=null, signature=TANbWl2fAoW0npNJj1QMMq8cloOGhmkeDaDFA8q5gWf8VhUPQcJ0OfedoIoHLR8Y7BGMMyKeYfvJDCQoOvVEW9Ip1sCjjlbz1DdZ2WJNdMVwbztRT8h01nHoPLiVFYgEi8rhxHLvRwjLBpS7x956Fk6NGRwvB5tfvKaHadubb0eLfDb6zW1UWIIRLHqT9lBYVa6PtzfZVE5tkacpJAcaOJRsj1A/yzO+X0Ux0lIQmsMTixTHkPiK6S2l1hAUFG4SuO+4poxPrQh1xdcAHXicPvt9/KN9MpnBIc5rCUURB3nFy9UmQoxuihJ45llXgswEIZV3MfquLvcoJri2zSaYAA==, originalJson={"productId":"ga_basic_lifetime","purchaseToken":"badkbmipdehdfnclebclcjpf.AO-J1Owp8f5cvBztQwOGJdi20ifz_Euz1znlTUP5Qi79Q2bSnUsCEIjww1fqLMob31i-P0PJ3uR2Qfs-tcEk3Fdy5htnhsl6pfmFVZXbhJ0fAgPkalOjyULNn1bddcsEn_MV_egxiR4k","purchaseTime":1746651569660,"quantity":1,"developerPayload":null}, presentedOfferingContext=null, storeUserID=null, purchaseType=GOOGLE_RESTORED_PURCHASE, marketplace=null, subscriptionOptionId=null, replacementMode=null). Error: PurchasesError(code=UnknownBackendError, underlyingErrorMessage=Backend Code: 7651 - The payment for this non-subscription product is not complete., message='There was an unknown backend error.')

 

2 replies

Forum|alt.badge.img
  • Author
  • New Member
  • 1 reply
  • May 9, 2025

I’ve noticed that the user ID changes when migrating from the old API to the new API—it’s as if the app treats the user like they just uninstalled and reinstalled it.

That’s the issue I’m running into. I’m not sure if that’s the intended behavior, but the only way I’ve found to fix it is by explicitly setting the user ID in the purchase configuration.


wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 297 replies
  • May 15, 2025

Hi! I apologize for the wait. I took a look internally regarding this issue. It looks like the Engineering team identified an issue with cases where the cache would be invalidated after migrating versions of the SDK. They shipped a fix for this in iOS version 4.17.0 (which would be applied in version 4.8.0 for our Flutter SDK). Can you let me know which version that you are attempting to update to?

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings