There is a new dropdown and button for selecting your desired UI solution in the Project Settings - making use of this goes over all Simple IAP System script files and e.g. replaces Unity UI references to TextMeshPro (Text > TextMeshProUGUI). Currently also InputField > TMP_InputField.

It is easily extendable with more classes or even a completely different UI asset, you just have to maintain the source and target types in the UISourceConverterData script. Note that the scenes included still make use of Unity UI, so after converting all references to TextMeshPro they will not work anymore. The converter is designed for when you are using your own shop scenes, or did the conversion manually already, but want to upgrade Simple IAP System at some point. You could basically do a "Replace All" in Visual Studio for that, but it is built-in now with that option.

Added in 5.0.3
https://flobuk.com/forum/post/12344

Added in 5.0.3
https://flobuk.com/forum/post/12344

how do i know if i succecssfully make connection with Playfab API

If you are not using "Validation Only", you'll have to login the user with PlayFab before showing the store. You can use the sample login scene included for testing this.
With "Validation Only" enabled on the PlayFabManager, you would just try to purchase a product in your shop (on a mobile device - there are no receipts in the Unity Editor).

Hello Ben,

restoring purchases on a physical device (e.g. Android or iOS) communicates with the respective App Store to retrieve purchase receipts, which are then send to PlayFab for re-validation. In fact, a restore is treated as a new purchase since it invokes the regular purchase process. PlayFab then detects it as a duplicate.

Restoring with PlayFab is not really a thing anyway, because when logging into the account, you get all products associated with it. Users just need to login with the same email or username as before. So it makes sense to make sure they can retrieve their PlayFab account, not so much individual receipts.

for each product, did you add a real money or virtual currency in the costs section?
No real money or virtual currency was added. We kept this section empty.

Then that's the issue: a product that exists on an App Store needs a "Real Money" currency added, even if the price string is empty. The reason is that not all products are requested from the App Store, but specifically those that contain a "Real Money" currency are. Without any costs, the product is granted to the user automatically since it is deemed as free (this was also the previous behavior).

Line 4, so it fails directly at the "using SIS;" in your script? How... please let me know what's wrong with that, if you stumble over a solution!

@baron Thanks for confirming that for me.