Unity Services Window: Users can install and update in the Cloud Services window, under In-App Purchasing, by pressing the ‘Import’ or ‘Update’ button.
Asset Store: Unity IAP is now also available on the Asset Store at http://u3d.as/xM1.
Changes (Changelog.md in the Assets/Plugins/UnityPurchasing folder):
See the last post on this thread for the latest fixes and features to Unity IAP.
Tizen Store problem:
I/Unity ( 3565): Couldn’t open /opt/usr/apps/com.luabingo.luabingo/lib/libTizenStore.so, error: /opt/usr/apps/com.luabingo.luabingo/lib/libTizenStore.so: cannot open shared object file: No such file or directory
I/Unity ( 3565):
I/Unity ( 3565): (Filename: Line: 192)
I/Unity ( 3565):
I/Unity ( 3565): Couldn’t open /opt/usr/apps/com.luabingo.luabingo/lib/libTizenStore.so, error: /opt/usr/apps/com.luabingo.luabingo/lib/libTizenStore.so: cannot open shared object file: No such file or directory
I/Unity ( 3565): at (wrapper managed-to-native) UnityEngine.Purchasing.TizenStoreBindings:setUnityPurchasingCallback (UnityEngine.Purchasing.UnityNativePurchasingCallback)
I/Unity ( 3565): at UnityEngine.Purchasing.TizenStoreBindings.SetUnityPurchasingCallback (UnityEngine.Purchasing.UnityNativePurchasingCallback AsyncCallback) [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.TizenStoreImpl.SetNativeStore (INativeTizenStore tizen) [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.StandardPurchasingModule.InstantiateTizen () [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.StandardPurchasingModule.InstantiateStore () [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.StandardPurchasingModule.Configure () [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.Extension.AbstractPurchasingModule.Configure (IPurchasingBinder binder) [0x00000] in :0
I/Unity ( 3565): at UnityEngine.Purchasing.Purchasing
What device or OS are you currently running this app on?
Can you confirm what version of the plugin you are using and how the plugin was installed? Are you seeing the “missing” plugin (libTizenStore) in the Plugins/UnityPurchasing/Bin/Tizen folder?
Hi,
Why do you removed the “select store at runtime”?! It was very useful feature for me and helped me to save time and avoid submitting my app with the wrong Target Store selected!
Please restore this feature in the coming update.
Hi @00christian00 ! CloudMoolah is a content and IAP payment aggregator, and partner of Unity’s, recently founded to help developers more easily access the complicated Asian market, focusing on Southeast Asia initially.
They maintain a digital wallet for users fillable by users through a range of payment providers active in Asia, such as MOL. The diverse range of payment providers matches how that market spends money through mobile.
Their team has joined us this week at Unite LA to talk about their new company in a Session (November 1, Breakout 2, site) and on the showroom floor.
This app store and IAP solution is currently targeting Android games.
I understand the wallet thing, but what mean content aggregator? Are they offering an alternative store?
Because I don’t think you can have alternative payment methods on Google Play store.
@Wadjey It’s just the menu item that’s gone; nothing changed in code. You can still select your Android store at runtime by passing the desired AndroidStore over to the StandardPurchasingModule.Instance at initialization.
Sorry for being unclear - yes all of that is correct. Cloud Moolah supports distributing applications, and collects payments from several third party payment providers into a Cloud Moolah digital wallet.
IAP library automatically adding READ_PHONE_STATE permission for android.
Repro:
create empty unity project
enabled services
import IAP library from services tab
Verification:
build to android project
look in ProjectFolder/ProjectName/AndroidManifest.xml
you will note the permission does not exist before adding the library, but is automatically included afterward.
This did not happen with the previous IAP library (we updated recently to fix the google IAP sandbox bug).
Any chance anyone can confirm this? I’ve tested my code paths for sandbox, but will probably revert to old IAP library to fix this and the outstanding moolah issue with WebViewClient.onReceivedSslError
Most plugins that use native libraries will not work correctly in the Emulator and IAP falls into that category. With respect to “next steps” here it depends on how you were planning to use the Emulator. You can manually swap-out the Tizen store DLL for the “stubbed” version which will eliminate this dependency, but any code that attempts to actually use IAP will then throw an exception.