Hi there,

Yes, I do know that SDKBOX is useless. However, is there any likelihood 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 seen this significant issue.

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 isn’t simple.
There are important API adjustments between model 4 and model 5, and the strategies obtainable in model 4 have been deprecated.
So, in follow, model 5 assist is a should.

Unfortunately, there is no such thing as 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 unsuitable data.
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 should 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 should face such points any extra.
I can’t share my code, o/w i’d enable you to.

In conclusion, I feel the one method 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 to your replies. Yeah, that is the very best time to spend few days on the wrapper. It will likely be additionally an excellent time to combine different shops (Amazon, Huawei, Samsung and so on.).

@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.

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 possibly can work on it your self and share it.
Also, I can’t make it totally appropriate 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.

Note that it’s only for Android and never totally appropriate with sdkbox::IAP.
The callback arguments and namespace are completely 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 conversant in Android at this level.
For iOS, you possibly can proceed to make use of sdkbox::IAP, so you possibly can determine the platform and use
I’m considering of utilizing my very own code for android and sdkbox::IAP for iOS.

Thanks to your share.
did you check in googleplay? and its work?

Of course, I really made a check buy on Google Play.
It works fantastic.

Hello, it ‘s works for android. Please replace for IOS. i would love exchange 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 challenge for Android.
Works properly.

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