ArgumentException: Cannot set currency to an empty or null string

I'm getting 'ArgumentException: Cannot set currency to an empty or null string' trying to implement codeless IAP.

It looks like I've just forgotten to complete a currency somewhere, but I can't seem to find it. Anyone seen this anywhere?

I'm using Unity 2018.1.0f2 if it matters.

Spoiler: Full error text

ArgumentException: Cannot set currency to an empty or null string
UnityEngine.Analytics.Analytics.Transaction (System.String productId, Decimal amount, System.String currency, System.String receiptPurchaseData, System.String signature, Boolean usingIAPService) (at C:/buildslave/unity/build/Modules/UnityAnalytics/UnityAnalytics.cs:134)
UnityEngine.Purchasing.UnityAnalytics.Transaction (System.String productId, Decimal price, System.String currency, System.String receipt, System.String signature) (at /Users/stevenb/unity-src3/Extensions/UnityPurchasing/Runtime/Purchasing/UnityAnalytics.cs:14)
UnityEngine.Purchasing.AnalyticsReporter.OnPurchaseSucceeded (UnityEngine.Purchasing.Product product) (at /Users/stevenb/unity-src3/Extensions/UnityPurchasing/Runtime/Purchasing/AnalyticsReporter.cs:27)
UnityEngine.Purchasing.StoreListenerProxy.ProcessPurchase (UnityEngine.Purchasing.PurchaseEventArgs e) (at /Users/stevenb/unity-src3/Extensions/UnityPurchasing/Runtime/Purchasing/StoreListenerProxy.cs:33)
UnityEngine.Purchasing.PurchasingManager.ProcessPurchaseIfNew (UnityEngine.Purchasing.Product product) (at /Users/stevenb/unity-src3/Extensions/UnityPurchasing/Runtime/Purchasing/PurchasingManager.cs:211)
UnityEngine.Purchasing.PurchasingManager.OnPurchaseSucceeded (System.String id, System.String receipt, System.String transactionId) (at /Users/stevenb/unity-src3/Extensions/UnityPurchasing/Runtime/Purchasing/PurchasingManager.cs:115)
UnityEngine.Purchasing.JSONStore.OnPurchaseSucceeded (System.String id, System.String receipt, System.String transactionID)
UnityEngine.Purchasing.FakeStore.<>n__0 (System.String id, System.String receipt, System.String transactionID)
UnityEngine.Purchasing.FakeStore+<>c__DisplayClass15_0.<FakePurchase>b__0 (Boolean allow, PurchaseFailureReason failureReason)
UnityEngine.Purchasing.UIFakeStore+<>c__DisplayClass14_0`1[UnityEngine.Purchasing.PurchaseFailureReason].<StartUI>b__0 (Boolean result, Int32 codeValue)
UnityEngine.Purchasing.UIFakeStore.OkayButtonClicked ()
UnityEngine.Purchasing.UIFakeStore.<InstantiateDialog>b__16_1 ()
UnityEngine.Events.InvokableCall.Invoke () (at C:/buildslave/unity/build/Runtime/Export/UnityEvent.cs:166)
UnityEngine.Events.UnityEvent.Invoke () (at C:/buildslave/unity/build/Runtime/Export/UnityEvent_0.cs:58)
UnityEngine.UI.Button.Press () (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/UI/Core/Button.cs:36)
UnityEngine.UI.Button.OnPointerClick (UnityEngine.EventSystems.PointerEventData eventData) (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/UI/Core/Button.cs:45)
UnityEngine.EventSystems.ExecuteEvents.Execute (IPointerClickHandler handler, UnityEngine.EventSystems.BaseEventData eventData) (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/EventSystem/ExecuteEvents.cs:50)
UnityEngine.EventSystems.ExecuteEvents.Execute[IPointerClickHandler] (UnityEngine.GameObject target, UnityEngine.EventSystems.BaseEventData eventData, UnityEngine.EventSystems.EventFunction`1 functor) (at C:/buildslave/unity/build/Extensions/guisystem/UnityEngine.UI/EventSystem/ExecuteEvents.cs:261)
UnityEngine.EventSystems.EventSystem:Update()

 

The same for me. I got this on the working project after updating to 2018.1.

 

@ap-unity

When could we expect the future version release?

 

Thanks. I'll work in another direction for now, and hopefully the bug is resolved the next time I cycle back to IAP.

 

How to fix it?

 

@phpnato Unfortunately I'm still seeing the exception in IAP 1.19, so you would need to wait for the next release. Is it preventing the purchase to complete on the device for you?

 

Yes. There is an error while purchasing.

 

@phpnato Understood, the IAP team is working on it, no ETA yet but I will keep this thread updated.

 

As I understand it, the purchase succeeds, and then we get an exception while trying to send this event to Analytics:

 

Are those purchase registered or they fail?

 

I've reverted to 2017.4. Unless you need a new feature, this seems to be the best fix.

 

the same problem with working project. is it possible to solve the problem with 2018.1.f1 or the only way is to go back to old version?

 

Please see my post from May 23, we are working on a resolution.

 

Thank you

 

Almost two weeks later and the bug still isn't fixed. A bug that any decent QA should've been able to catch. Things like this are why my company wants to move to other game engines - Unity just feels like it's in perpetual beta.

 

The fix is currently going through QA, we want to make sure it properly addresses the issue. Our test matrix with various store platforms, device platforms and Unity versions is quite large, and takes time.

 

Still no fix for this?

 

We are working on this issue at highest priority. I personally ensured yesterday that this is the first issue to be addressed. We are currently scheduling the fix into the release cycle.

 

Thank you.

 

I'm also facing the same problem. @JeffDUnity3D Please post here when the fix is released.

 

How can I turn off Analytics so it doesn't try to send out the "null string"? Any work around so we can get back to IAP development?

 

This is sad, because we've completed our game and waiting for the release. Can't test IAP, can't publish the game.

 

The delay to solve the problem is ridiculous. This problem can cause great financial loss. What is the deadline to solve this?

 

The delay is due to the fact that it involves a change to the Editor in addition to the IAP package. We are trying to coordinate and test the required changes, and it's taking longer than expected.

 

We need workaround too. Who know it?

 

@newwise A workaround, and as reported by others here, would be to consider using Unity 2017 where the issue should not occur.

 

ap-unity, Thank you for the info. This will help a lot

 

@ap-unity thanks for the help.

1. Asset store says IAP is v1.19, but package manager says 2.0.3. I originally installed IAP via asset store, but since it has shown up as in-project in the package manager I recently updated it from there. But the discrepant version numbers are confusing. Do you have any advice about managing the IAP asset from the store vs. package manager?
2. Is there an ETA for IAP v1.20 when this bug will be fixed?
3. I don't quite understand what you mean by "test the behavior when the purchase is complete separately from the actual ProcessPurchase call". Could you provide an example? Are you saying do not add a callback to OnPurchaseComplete in the inspector?

 

Thanks for the reply. I'd like an explanation or example for this one, too.

Thanks again.

 

Thanks for the detailed reply. But the thing is I'm not trying to see if the after-purchase codes work or not. The IAP button script is not working on the test devices either. It's not an editor only problem. My Google Play Store beta test users can't purchase the IAP, so that's not editor only.

Thanks for the replies and great work.

 

Actually it's the same error I'm getting:
ArgumentException: Cannot set currency to an empty or null string

So I'll continue following this thread.

 

@thecotanak Can you post your device logs that contain this exception?

https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/

https://forum.unity.com/threads/how-to-capturing-device-logs-on-ios.529920/

 

@JeffDUnity3D Sorry, it turns out that's our mistake.

We've tested on Play Store closed alpha and after correcting the license test emails, it worked fine on device.

Thanks.

 

I am getting this same error, using the scripting API in the current beta version, when testing from the editor. I am using the IAP package version 2.0.3 This is on a game that is currently working just fine in my release version on Google Play and the Amazon App Store.

I am making some updates, and doing some testing with the current beta, and just wanted to confirm if this problem still exists, or what I might be doing wrong. I have not made any changes to the purchasing code between the version that works, and the version that doesn't. The only difference I can see is the version of Unity I am working with.

Any help is appreciated!

Thanks,
-Larry

 

@Larry-Dietz Please see previous mentions that this only happens in the Editor, and work around was provided. Yours might be a new issue, please provide steps to reproduce with a new project.

 

Sorry to take so long to get back to this. I ended up blowing out all the IAP code, and reinstalling the IAP unitypackage, and everything finally started working. Reinstalled the same version that I blew out, so no idea what was wrong. I have to assume that a file got corrupted somehow.

Thanks,
-Larry

 

I am also getting the same error in the Latest Version Unity 2018.3.17. How to resolve this error... In editor only.
in Codeless IAP When i click the subscription and it emits fake store. When i click the buy. This error works. if i click cancel No Error Shows.

Why the error Continues STILL in the latest version also???????????...