Skip to main content
Solved

KMP SDK Warning: Could not resolve remote config blob(s) for 4 of 4 requested item(s) in topic 'ui_config'

  • August 9, 2026
  • 5 replies
  • 46 views
L
Forum|alt.badge.img+1

Our users' devices report A LOT of these warnings after we updated to the latest KMP SDK:

[Purchases] - WARN: Could not resolve remote config blob(s) for 4 of 4 requested item(s) in topic 'ui_config': [app, localizations, variable_config, custom_variables]. Returning null.

 

These are new in our latest Android release, and we're getting 1000s of them reported on Sentry. We haven't changed anything in our RevenueCat config/account, just updated the SDK.

Current SDK versions (in which the warning occurs):

  • com.revenuecat.purchases:purchases:10.16.0

  • com.revenuecat.purchases:purchases-kmp-core:3.4.0

  • com.revenuecat.purchases:purchases-kmp-core-android:3.4.0

  • com.revenuecat.purchases:purchases-kmp-mappings-android:3.4.0

  • com.revenuecat.purchases:purchases-kmp-models-android:3.4.0

Previous release contained these SDK versions (warning doesn't occur):

  • com.revenuecat.purchases:purchases:10.14.1

  • com.revenuecat.purchases:purchases-kmp-core:3.3.1

  • com.revenuecat.purchases:purchases-kmp-core-android:3.3.1

  • com.revenuecat.purchases:purchases-kmp-mappings-android:3.3.1

  • com.revenuecat.purchases:purchases-kmp-models-android:3.3.1

 

Any advice/hints what this could mean, and how to fix it, whether it's a bug in the SDK or something we need to address?

 

Best answer by matt-heaney

Hey there,

 

Thank you for the follow-up.

 

Yes, I can confirm these errors will also be cleaned up. The fixes for these errors have already been released in the latest Android SDK, so they will be included in the upcoming KMP release.

 

I confirmed with the engineering team on the expected release timeline for these changes.

 

There is a KMP SDK release planned for later this week. This will include the fix for the "[Purchases] Failed to read ui_config before getOfferings; proceeding without it." error.

 

The fix for the "WARN: Could not resolve remote config blob(s)" warning is expected to be included in the following KMP SDK release, which is currently planned for next week.

 

I will update this thread when both fixes have been released and are ready to use.

 

I hope this helps! If there is anything I can do to help in the meantime, please let me know!

 

Thanks!

    5 replies

    matt-heaney
    RevenueCat Staff
    Forum|alt.badge.img+6
    • matt-heaney
    • RevenueCat Staff
    • August 10, 2026

    Hey there,

     

    Matt from RevenueCat here! Thank you for the detailed version information!

     

    I’ve taken a look into this, and I can confirm that this warning is SDK logging noise rather than an issue with your RevenueCat project configuration. Your offerings and purchases should continue to work as expected.

     

    This started appearing after your purchases-kmp 3.3.1 → 3.4.0 update because 3.4.0 uses Android Purchases 10.16.0, which introduced this additional logging when fetching offerings.

     

    The good news is that this has already been cleaned up and will be released in an upcoming version of the SDK. I will make sure to update this forum thread when the release is live.

     

    Alternatively, if your offerings and purchases are working correctly, it’s safe to filter this warning from Sentry for now. You don’t need to make any changes to your RevenueCat dashboard.

     

    If you are seeing any actual purchase or offerings issues alongside the warning, please send over your RevenueCat project ID and a sample App User ID, and I’ll be happy to take a closer look!

     

    Thanks!

    Matt, Developer Support Engineer @ RevenueCat
      L
      Forum|alt.badge.img+1
      • lw-trsc
      • Author
      • New Member
      • August 10, 2026

      Hi Matt, thanks for the reply and the fix!

       

      I now noticed it's also reporting ERROR logs / exceptions from the same or a related issue:

      [Purchases] Failed to ready ui_config before getOfferings; proceeding without it. 

      Exception:

      java.lang.IllegalStateException: Required value was null.
          at com.revenuecat.purchases.common.workflows.WorkflowManager$onPaywallConfigReady$readiness$1$1$1.invokeSuspend(WorkflowManager.kt:139)
          at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
          at kotlinx.coroutines.UndispatchedCoroutine.afterResume(CoroutineContext.kt:278)
          at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:101)
          at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:47)
          at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:35)
          at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:101)
          at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:47)
          at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
          at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.java:124)
          at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
          at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
          at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:798)
          at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
          at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

      These can probably also get ignored. Can they also get cleaned up / dropped in the SDK?

       

      Unfortunately, we can't filter on Sentry side (Team plan doesn't allow custom inbound filters), so we have to wait for the new release. Or we'll downgrade temporarily to the previous SDK version until it's released if it takes longer.

      matt-heaney
      RevenueCat Staff
      Forum|alt.badge.img+6
      • matt-heaney
      • RevenueCat Staff
      • Answer
      • August 11, 2026

      Hey there,

       

      Thank you for the follow-up.

       

      Yes, I can confirm these errors will also be cleaned up. The fixes for these errors have already been released in the latest Android SDK, so they will be included in the upcoming KMP release.

       

      I confirmed with the engineering team on the expected release timeline for these changes.

       

      There is a KMP SDK release planned for later this week. This will include the fix for the "[Purchases] Failed to read ui_config before getOfferings; proceeding without it." error.

       

      The fix for the "WARN: Could not resolve remote config blob(s)" warning is expected to be included in the following KMP SDK release, which is currently planned for next week.

       

      I will update this thread when both fixes have been released and are ready to use.

       

      I hope this helps! If there is anything I can do to help in the meantime, please let me know!

       

      Thanks!

      Matt, Developer Support Engineer @ RevenueCat
        L
        Forum|alt.badge.img+1
        • lw-trsc
        • Author
        • New Member
        • August 11, 2026

        Great - thanks Matt for the quick follow-up and upcoming fixes 🚀

        Sounds good from here then 👍

          matt-heaney
          RevenueCat Staff
          Forum|alt.badge.img+6
          • matt-heaney
          • RevenueCat Staff
          • August 12, 2026

          I’m delighted to have helped ​@lw-trsc!

           

          As mentioned, I’ll share updates on this thread over the coming weeks as each new version of the SDK is released!

           

          Thanks again!

          Matt, Developer Support Engineer @ RevenueCat
          Terms & ConditionsAccessibility statement