Purchasing: the name StandardPurchasingModule does not exist in current context

[Jonsi]

@Janibasha

To fixed it, just go the folder ‘UnityPurchasing’ folder in ‘Plugins’ folder. Then double click on the package Unity IAP. Import all and the problem solved. If it does fix your problem just try Dong Nguyen solution.

Thanks!This worked for me.

[shoridevel]

Solve: You must import in this order.

1. IAP On.
2. IAP import.
3. Your sourcecode import.

[austinborden]

In my case I was getting the error from a test class that has an asmdef. I had to add UnityEngine.Purchasing.dll and Stores.dll to the references and the error went away.

[jimbojimbo82]

@mattbrandmm

Yes I did that. Thank you.

The solution ended up being to comment out the lines that were preventing compilation, then Unity gave a popup to install IAP, which I did, including importing, and then I was able to uncomment out the lines that it was complaining about.

Thank you this worked a treat!!!

[JeddJedd]

Skyboard you’re a lifesaver. Importing manually fixed it. Thank you.

[ferranases]

@mattbrandmm

Yes I did that. Thank you.

The solution ended up being to comment out the lines that were preventing compilation, then Unity gave a popup to install IAP, which I did, including importing, and then I was able to uncomment out the lines that it was complaining about.

That work for me.
Commented the lanes that give me errors, then the project compile in Unity and show you to install things, and then come back to uncoment the code

[Darknesssss]

@mattbrandmm

Yes I did that. Thank you.

The solution ended up being to comment out the lines that were preventing compilation, then Unity gave a popup to install IAP, which I did, including importing, and then I was able to uncomment out the lines that it was complaining about.

Thanks in 2020 my friend

[wa4lnut]

@Skyboard_Studios

When you hit the Reimport button you will see that in your Plugins\UnityPurchasing folder you have a singular file that you can further import.

On import you will see

Interesting how I did this a couple times as I had the same error as you and nothing worked until I ran the UnityIAP manually…

Hope that helps.

Update in 2018 I ran across this anoying message saying must update… and I ignored it for a few months… and then just today I decided to walk down the road up updating my IAP and I had to delete the UnityPurchasing Folder / restart Unity… / Import the Asset from the Above Image. / then manually importing the secondary asset that is in the root of the UnityPurchasing directory.

This last go of reupdating took a couple tries and I had to per persistent. Felt like at least 3 cycles of the “Hey your IAP is outdated… You want to update?” dialogues… But at this momement all seems ok.

Thanks, that worked for me in unity 2019.3

[aldawoodimustafa]

@mattbrandmm

Yes I did that. Thank you.

The solution ended up being to comment out the lines that were preventing compilation, then Unity gave a popup to install IAP, which I did, including importing, and then I was able to uncomment out the lines that it was complaining about.

Great + BIG LIKE

[JeffDUnity3D]

I noticed the same thing! I just deleted the files that were showing the errors. After deleting the last one, the installer magically started. Interesting. FYI the best forum to post IAP issues is here Unity Services - Unity Discussions

[sama-van]

@austinborden

In my case I was getting the error from a test class that has an asmdef. I had to add UnityEngine.Purchasing.dll and Stores.dll to the references and the error went away.

Very good catch, it didn’t even cross my mind P_P…!! Works a charm now!

[dean0]

@austinborden

In my case I was getting the error from a test class that has an asmdef. I had to add UnityEngine.Purchasing.dll and Stores.dll to the references and the error went away.

Yes! Many thanks for that tip.

If you are using unity purchasing from an assembly, make sure you add Assembly Definition References to Unity.Purchasing, AND UnityEngine.Purchasing.Stores

[Golkar_Asghar]

@Skyboard_Studios

When you hit the Reimport button you will see that in your Plugins\UnityPurchasing folder you have a singular file that you can further import.

On import you will see

Interesting how I did this a couple times as I had the same error as you and nothing worked until I ran the UnityIAP manually…

Hope that helps.

Update in 2018 I ran across this anoying message saying must update… and I ignored it for a few months… and then just today I decided to walk down the road up updating my IAP and I had to delete the UnityPurchasing Folder / restart Unity… / Import the Asset from the Above Image. / then manually importing the secondary asset that is in the root of the UnityPurchasing directory.

This last go of reupdating took a couple tries and I had to per persistent. Felt like at least 3 cycles of the “Hey your IAP is outdated… You want to update?” dialogues… But at this momement all seems ok.

It’s working solution. Tnk u.

[DhiaSendi]

Unity 2020.3.34
For anyone upgrading to a newer Unity version I managed to fix the issue by :
1- Make sure the IAP is on under “Services” (Window/General/Services)
2- Delete the folder "Assets/Plugins/UnityPurchasing
3- Comment the lines with errors or simply cut/past the whole class somewhere else, wait the editor to recompile then get back the class

[andrew_pearce_1]

Since I migrate from Unity 2018.4 to 2020.3 I faced the problem with missing StandardPurchasingModule (the same error was with 2021). If you are also using assemblies, then do not forget to add another assembly “UnityEngine.Purchasing.Stores”. In past, it was enough to have only “UnityEngine.Purchasing”. I hope it will saves sometimes time.