Resolved Error: Required to have a value for transactionName

After I updated my Unity In-App Purchases package to 4.2.1 I keep getting this error whenever I make a purchase in the editor using the Fake store UI. I'm afraid it will follow my actual purchases as well. Any suggestions?

 

the same error in editor, I just update my unity to 2020.3.37f1, and iap package to 4.2.1, and I finally found this is not a bug.

the stacktrace in editor is :

Required to have a value for transactionName
UnityEngine.Debug:LogError (object)
Unity.Services.Analytics.AnalyticsServiceInstance:Transaction (Unity.Services.Analytics.TransactionParameters) (at Library/PackageCache/com.unity.services.analytics@4.0.1/Runtime/Events/Transaction/AnalyticsServiceInstance.Transaction.cs:19)
UnityEngine.Purchasing.PurchasingManager:InitiatePurchase (UnityEngine.Purchasing.Product)​

I just called "m_StoreController.InitiatePurchase(product)" as the same as the demo.

After check the internal code, it is because the new version of iap package will require the product "title" in the IAP Catalog config, where I left it null, then it will show the error log.

 

You are going to suggest not using codeless. I've seen your answer in almost all the posts that mention codeless. Until Unity removes codeless or makes it deprecated please put this suggestion as a comment.

We are using a reliable way of implementing IAP with plenty of resources online. If you want to answer with "don't use Codeless" then describe the detailed process of the solution without it, not just say it.

 

For you it's not an alternative, it's mandatory. You cannot expect people to go back on changing their whole implementation a week before release.

 

I got the same error about transactionName.
I started over following Jeff's sample code, and the error went away.
I'm not sure what changed, but my GUESS is that I had not filled in anything in the "Title" slot of the "IAP Catalog" dialog in the Unity Editor. When I re-did it all, I went ahead and copied both "Title" and "Description" from what I had in the Google Play Store.

So maybe try that I guess.

 

I don't understand. I released the game using Codeless. Everything worked. You still have this method listed in your documentation.
https://docs.unity3d.com/Packages/com.unity.purchasing@4.4/manual/Overview.html

Today I needed to add a new purchase urgently and I get a similar error.

In this post you say that Codeless can no longer be used. But why you don't mention it anywhere? There is no news?

 

@JeffDUnity3D

Strongly believe this "Required to have a value for transactionName" error is happening in 4.4.1 when calling:

• ProductCollection.WithID
• IAppleExtensions.RestoreTransactions

As far as I can tell, I merely use the ConfigurationBuilder to pass in an id and type. There's no "transaction name" I've ever had to deal with...?

This is all via scripting. I do not use the Codeless thing.

Error happens on native iOS builds.
Calling IAppleExtensions.RestoreTransactions seems to trigger the error easily.

Unable to reproduce in the Editor (2021.3.9f1).

Although this is getting thrown as an "error", it doesn't seem to affect any functionality negatively. Purchases and restores still work. Feels like it's an async error somewhere behind the scenes.

Stack trace:

Code (csharp):

1. Unity.Services.Analytics.AnalyticsServiceInstance:Transaction(TransactionParameters)
2. UnityEngine.Purchasing.AnalyticsAdapter:SendTransactionEvent(Product)
3. UnityEngine.Purchasing.AnalyticsClient:OnPurchaseSucceeded(Product)
4. UnityEngine.Purchasing.StoreListenerProxy:processPurchase(PurchaseEventArgs)
5. UnityEngine.Purchasing.PurchasingManager:processPurchaseIfNew(Product)
6. UnityEngine.Purchasing.Extension.UnityUtil:Update()

 

Not using the sample code.

As a rough glimpse:

Code (csharp):

1. IExtensionProvider unityStoreExtensionProvider; // gets assigned via IStoreListener.OnInitialized
2.  
3. ...
4.  
5. var apple = unityStoreExtensionProvider.GetExtension<IAppleExtensions>();
6. apple.RestoreTransactions((restorationFinishedWithoutError) => {
7.     if (restorationFinishedWithoutError) {
8.         // Restoration successful, though potentially nothing was actually restored
9.     }
10.     else {
11.         // Error restoring
12.     }
13. });
14.  

restorationFinishedWithoutError ends up being true, despite the error being thrown.

 

Sounds plausible.

Yes, the restore process works. From a fresh App Store sandbox account, did a new purchase (which triggered the error somewhere I believe), uninstalled the iOS app, reinstalled, did a restore (again triggering the error), and the restore worked.

I haven't looked at the Unity Dashboard with all this, but the transactions get retrieved successfully within the code despite the error.

 

Thanks for testing.

I don't use the Analytics at all.

I initialize with Unity Gaming Services, but just for the store:

Code (csharp):

1. try {
2.     var options = new InitializationOptions().SetEnvironmentName("production");
3.     await UnityServices.InitializeAsync(options);
4. }
5. catch (System.Exception e) {
6.     // An error occurred during services initialization.
7.     Debug.LogWarning($"WARNING: UnityGamingServices.Start: Failed to initialize. Exception: {e}");
8. }

 

So what to do for fixing that? I have this error to

 

The same problem

 

So can we safely ignore the error and publish without a problem or should we try to implement the sample IAP?