Skip to main content

Hello!

What versions of Unity does RevenueCat support? 

The RevenueCat SDK installed correctly on a few of my projects running on older versions of Unity. I tried installing the SDK on Unity version 6000.019f1 but the External Dependency Manager does not show under the Edit menu like it does with the projects running on older versions of Unity.

I’m following the instructions from here: https://www.revenuecat.com/docs/getting-started/installation/unity

I’ve tried to install the SDK with both Option 1 (recommended): Install using OpenUPM and Option 2: Import the Purchases Unity package.

As suggested in the documentation, I have tried reinstalling the RevenueCat plugin and manually importing the EDM4U plugin (multiple times) but the External Dependency Manager still does not show under the Edit menu in Unity.

Curious if anyone-else has encountered this issue or has any insight. Thanks!

 

 

Have you tried the OpenUPM CLI route yet?

If you prefer, you can also use OpenUPM-CLI to add the scoped registry and the package through the command line. To do that, install the OpenUPM-CLI if you haven't already, then run openupm add com.revenuecat.purchases-unity. That should be it!

 

Also, which version of EPM4U are you using?

Hi Ryan,       

Thanks for the reply. I’m using EPM4U version 1.2.183. 

After installing the OpenUPM-CLI, and then running openupm add com.revenuecat.purchases-unity. I get the following warning:

  • WARN editor.version 6000.0.19f1 is unknown, the editor version check is disabled

As a test, I went back one version in Unity with the same project version 2023.2.20f1 ran openupm add com.revenuecat.purchases-unity and I didn’t get the warning message about the unknown editor. 

  • notice added com.revenuecat.purchases-unity@7.2.0
  • notice please open Unity project to apply changes.

Appreciate the help! Please let me know if you would like me to run any other tests.  

To clarify, after installing this way, are you able to use our SDK despite the warning? I’ll look into this warning either way, but am curious whether it’s blocking or not

Hi Ryan! Thanks for following-up with me. I updated the Unity version for the Subtester example to Unity version 6000.019f1 and the External Dependency Manager is showing under the Edit menu with no errors.

The Subtester also runs on the Xcode simulator and on a device correctly. I’ll try updating a few of my other Unity projects to this version and see if I encounter any issues. Appreciate the help!

Best,

-DJ

Terms & ConditionsCookie settings