Replace to Billing Library 4(sdkbox) – Third-Occasion

Hello there,

Sure, I do know that SDKBOX is lifeless. Nevertheless, is there any likelihood 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.

Greatest,
kds

I too have seen this major problem.

As everyone knows, SDKBOX is lifeless.
Most likely no replace is predicted.

Reminder: Beginning 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 will not be simple.
There are important API adjustments between model 4 and model 5, and the strategies out there in model 4 have been deprecated.
So, in apply, model 5 help is a should.

Sadly, there isn’t any open supply library out there at the moment that I can hope to seek out.

• In a position to management each iOS and Android with a standard interface.
• Assist each cocos2d-x 3.x and 4.x
• Appropriate with Billing Library model 5

From the place did you discover this? You will have completely unsuitable information.
I do have my very own framework written, beforehand it was on model 4 and not too long ago i upgraded to version-5 and that i dont need to do any apis adjustments in any respect.

Beforehand i used to be additionally utilizing sdkbox, however attempt to create your personal 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 allow you 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 Goal-C, so it’s an unknown.

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

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

Hey, 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’re in a rush you’ll be able to work on it your self and share it.
Additionally, I can not make it absolutely suitable with sdkbox::IAP.
I’ll solely implement the options that I take advantage of.

It isn’t excellent, however I used to be in a position to create the performance I wanted.
I want to share it as a pattern code.

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

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

If anybody else has applied the acquisition performance, please share.

I’m solely conversant in Android at this level.
For iOS, you’ll be able to proceed to make use of sdkbox::IAP, so you’ll be able to establish 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?