Update to Billing Library 4(sdkbox) – Third-Party

Hi there,

Yes, I do know that SDKBOX is useless. However, is there any probability that you’re going to replace it to assist 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 predicted.

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

And the issue is just not straightforward.
There are important API adjustments between model 4 and model 5, and the strategies accessible in model 4 have been deprecated.
So, in observe, model 5 assist is a should.

Unfortunately, there isn’t any open supply library accessible right now that I can hope to search out.

• Able to regulate each iOS and Android with a typical 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 improper data.
I do have my very own framework written, beforehand it was on model 4 and just lately i upgraded to version-5 and that i dont need to do any apis adjustments in any respect.

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

In conclusion, I believe the one manner 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 in your replies. Yeah, that is the best time to spend few days on the wrapper. It shall be additionally time to combine different shops (Amazon, Huawei, Samsung and so on.).

@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 exchange 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 might be in a rush you may work on it your self and share it.
Also, I can not make it absolutely suitable with sdkbox::IAP.
I’ll solely implement the options that I exploit.

It is just not good, however I used to be in a position to create the performance I wanted.
I want to share it as a pattern code.

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

I don’t suppose you need to use this code as it’s, however you need to use it as a reference to implement the performance you want.

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

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

Thanks in 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 tremendous.