Hi there,

Yes, I do know that SDKBOX is useless. However, is there any probability that you will replace it to help Google Billing Library v4?

Ps. Google is forcing to make use of it ranging from 1.11.2022.

Best,
kds

I too have observed this major problem.

As everyone knows, SDKBOX is useless.
Probably no replace is anticipated.

Reminder: Starting on August 2, 2022, all new apps should use Billing Library model 4 or newer.
By November 1, 2022, all updates to current apps should use Billing Library model 4 or newer.

And the issue shouldn’t be simple.
There are important API adjustments between model 4 and model 5, and the strategies obtainable in model 4 have been deprecated.
So, in observe, model 5 help is a should.

Unfortunately, there isn’t a open supply library obtainable presently that I can hope to seek out.

• Able to manage each iOS and Android with a standard interface.
• Support each cocos2d-x 3.x and 4.x
• Compatible with Billing Library model 5

From the place did you discover this? You have completely incorrect data.
I do have my very own framework written, beforehand it was on model 4 and lately i upgraded to version-5 and that i dont must do any apis adjustments in any respect.

Previously i used to be additionally utilizing sdkbox, however attempt to create your personal wrapper class as soon as and also you dont must face such points any extra.
I can not share my code, o/w i’d show you how to.

In conclusion, I feel the one means to do that is to create my very own implementation of in-app billing for Android.
I’ve some expertise with native integration for Android, so I’ve began engaged on it.
If it really works, I want to share the code.

As for iOS, I’ve no expertise with Objective-C, so it’s an unknown.

Thanks on your replies. Yeah, that is the best time to spend few days on the wrapper. It will probably be additionally time to combine different shops (Amazon, Huawei, Samsung and so forth.).

@bluewind00 iOS integration ought to be simpler since you don’t have to make use of any “ndk”. I’ll share the code once I handle to do it (I hate Obj-C too :P). The precedence is Android, sdkbox nonetheless works on iOS.

Hello, I’m dealing with the identical drawback google billing 4 with use sdkbox. Please share supply code to interchange sdkbox for android

I’m nonetheless a piece in progress.
I’ll share it when it’s completed, however I can’t promise a deadline.
If you’re in a rush you may work on it your self and share it.
Also, I can not make it absolutely appropriate with sdkbox::IAP.
I’ll solely implement the options that I exploit.

It shouldn’t be good, however I used to be capable of create the performance I wanted.
I want to share it as a pattern code.

Note that it’s only for Android and never absolutely appropriate with sdkbox::IAP.
The callback arguments and namespace are totally different.

I don’t assume you should utilize this code as it’s, however you should utilize it as a reference to implement the performance you want.

If anybody else has carried out the acquisition performance, please share.

I’m solely conversant in Android at this level.
For iOS, you may proceed to make use of sdkbox::IAP, so you may determine the platform and use
I’m considering of utilizing my very own code for android and sdkbox::IAP for iOS.

Thanks on your share.
did you take a look at in googleplay? and its work?

Of course, I truly made a take a look at buy on Google Play.
It works advantageous.

Hello, it ‘s works for android. Please replace for IOS. i would really like change sdkbox is it not handy now

I’m not conversant in iOS.
Can somebody please share the code for the iOS buy course of.

I used sdkbox for ios, and used your venture for Android.
Works nicely.

https://github.com/newnon/avalon/blob/grasp/avalon/platform/ios/cost/cost.mm

Hello, i examined profitable on take a look at gadget. But after launch to manufacturing on google play retailer. Game crash

v4dUdD0okk04lr2Qt0FyTw==/split_config.arm64_v8a.apk!libMyGame.so (_JNIEnv::CallStaticObjectMethod(_jclass*, _jmethodID*, …)+108)
v4dUdD0okk04lr2Qt0FyTw==/split_config.arm64_v8a.apk!libMyGame.so (mingos::IAP::setListener(mingos::IAPEventListener*)+76)

Please examine proj.android/app/proguard-rules.professional.
The following description is required.

-keep class iap.** { *; }
-dontwarn iap.**

If an error happens within the launch construct even when these are described, I can not consider the trigger.

Hello, It’s fastened bug thank on your help.