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

Hello there,

Sure, I do know that SDKBOX is useless. Nonetheless, is there any likelihood that you will replace it to assist Google Billing Library v4?

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

Greatest,
kds

I too have observed this significant issue.

As everyone knows, SDKBOX is useless.
In all probability 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 just 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 observe, model 5 assist is a should.

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

• Capable of management each iOS and Android with a typical interface.
• Assist each cocos2d-x 3.x and 4.x
• Suitable with Billing Library model 5

From the place did you discover this? You will have completely flawed 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 should 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 should face such points any extra.
I can not share my code, o/w i’d enable you.

In conclusion, I feel 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 wish to share the code.

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

Thanks in your replies. Yeah, that is the best time to spend few days on the wrapper. It is going to be additionally 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.

Howdy, 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.
Additionally, I can not make it totally appropriate with sdkbox::IAP.
I’ll solely implement the options that I take advantage of.

It’s not excellent, however I used to be capable of create the performance I wanted.
I wish to share it as a pattern code.

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

I don’t assume 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 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 considering 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?

In fact, I truly made a take a look at buy on Google Play.
It really works high-quality.

Howdy, it ‘s works for android. Please replace for IOS. i would love exchange sdkbox is it not handy now

I’m not acquainted with 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 properly.

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

Howdy, i examined profitable on take a look at machine. However after launch to manufacturing on google play retailer. Sport 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 verify proj.android/app/proguard-rules.professional.
The next 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.

Howdy, It’s mounted bug thank in your assist.