Hi!
I’m trying to implement IAP on Tizen. I’ve tested Unity IAP in editor and on Android and it works great. But on Tizen I have some wierd behaviour.
After the UnityPurchasing.Initialize(this, builder); the touch input stops working. The app itself is still working but it’s ignoring input and neither OnInitialized nor OnInitializeFailed is called. If I switch scenes the touch input start to work again.
If I push back button the touch input also start to work again and I get logs:
I/Unity ( 1867): [UnityIAP] ProcessMessage subject: OnSetupFailed payload: NoProductsAvailable receipt: transactionId:
I/Unity ( 1867):
I/Unity ( 1867): (Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
I/Unity ( 1867):
I/Unity ( 1867): OnInitializeFailed InitializationFailureReason:NoProductsAvailable
I/Unity ( 1867):
I/Unity ( 1867): (Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
I/Unity ( 1867):
The logs are the same no matter if I have a dummy products added in the app or not.
It looks like UnityPurchasing.Initialize opens a fully transparent overlay that waits for something but never gets it
The another wierd thing is that if I’m swyping and tapping the screen for couple of minutes while it’s frozen, the input starts to work and outputs the log:
I/Unity ( 1678): BuyProductID FAIL. Not initialized.
I/Unity ( 1678):
I/Unity ( 1678): (Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)
My question is what the freak is happening here?
P.S.
I’ve tried Tizen IAP from Samsung Mobile but the sample code won’t compile because Tizen namespace is not recognized.
I’ve also read the [Closed] 1.8.1 Tizen IAPs - Unity Services - Unity Discussions topic but my case seams different.