Closed tajny closed 9 years ago
Not sure if this is related to gdx-pay directly. I think something with the OpenIAB/Samsung binding might not work as intented:
Does any of the solutions proposed there fix your problem?
Figured this out, it seems that this issue shows when there are two inapp services installed on device and openiab tries to guess the right one.
from https://github.com/onepf/OpenIAB/releases/tag/0.9.8
new 'store search strategy' options: installer(only the app installer can be a billing provider), installer then best fit (if the app installer is null or was uninstalled from the device the next suitable billing provider will be chosen), best fit (the choice is based on an options set) Amazon IAP 2.0 support Skubit store support Note: to emulate installation from a certain store, you need to install your app using adb install -i storepackage /path/to/yourapk
when installed from market ( not by adb ) everything is working as expected.
this happens on Android 5.0 , Samsung S5, Google Play 5.6.8
openiab-0.9.8.6
but on different test devices it works as expected
what the hell ? ;)