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

Hello @chuoihottieu, are you positive you haven’t modified the rest in your replace? Out of your logs it’s onerous to say what’s going on.

@bluewind00 Thanks for sharing, it’s a superb “base” for the long run enhancements. Please make it public once more

@PCCSOARES
@kds

Thanks.
I make it public the repository once more.
Once more, this can be a pattern and isn’t assured to work.

hello @kds @bluewind00
i change sdkbox::IAP with mingos::IAP comply with the directions, it’s work perfert on system help native arm64-v8a, however crash on armeabi-v7a with out motive.
for instance Samsung Galaxy A13 5G: ABI help: armeabi-v7a, armeabi.
Anyhow thanks you guys atleast i upgraded to billing v4 earlier than 1.11.2022!

chuoihottieu
Simply change
PROP_APP_ABI=arm64-v8a
with
PROP_APP_ABI=armeabi-v7a:arm64-v8a
in ‘proj.androidgradle.properties’

bluewind00, thanks very a lot so much (you might be our hero); I’ve up to date your code a bit, to get amount of bought merchandise; it really works even on Android 4.4.2. (debug and launch)

…Now I’ll attempt to insert it into my undertaking (appears not really easy).

These are information that may be copied immediately into your undertaking.

C++:

Courses/frequent/JsonParser.cpp
Courses/frequent/JsonParser.h
Courses/dropbox/json11/json11.cpp
Courses/dropbox/json11/json11.hpp
Courses/iap/MingosIAP.h
Courses/platform/android/Java_iap_PurchaseEventListener.cpp
Courses/platform/android/MingosIAP.cpp

Java:

proj.android/app/src/iap/Product.java
proj.android/app/src/iap/PurchaseEventListener.java
proj.android/app/src/iap/PurchaseManager.java

Subsequent is a set of information that will battle along with your undertaking’s code.
Please incorporate the required elements of your undertaking.

proj.android/app/src/org/cocos2dx/cpp/AppActivity.java
proj.android/construct.gradle
proj.android/app/construct.gradle
proj.android/app/proguard-rules.professional

After two days of crashes and black screens, eventually appears I used you code. It was onerous (for me), as a result of:

1. I used separate object (in my c++ code):

sdkbox::IAP::setListener(m_IAP_obj); // m_IAP_obj class extends : sdkbox::IAPListener

And you employ the primary class for the listener (object) :

class SampleScene : public cocos2d::Scene, public mingos::IAPEventListener { // your code
class HelloWorld : public cocos2d::Layer // my previous code

2. Additionally there are tiny distinction in:

proj.androidappsrcorgcocos2dxcppAppActivity.java
:
public class AppActivity extends Cocos2dxActivity { // your code
public class AppActivity extends com.sdkbox.plugin.SDKBoxActivity { // my code
…
mPurchaseManager = new PurchaseManager(this); // is it potential to vary this file to make use of as listener not AppActivity class (object), however one thing else?

Thanks in your nice job! Due to you, perhaps our Cocos video games shall be alive for some extra time.

This can be a crucial level, however so as to create your personal buy course of, you have to go away the sdkbox.
This implies making use of the next code to AppActivity.

public class AppActivity extends Cocos2dxActivity { 

Should you apply my code as it’s beneath, you’ll not obtain the notification after the acquisition request with my code.
It’s because SDKBoxActivity will obtain the results of the method from the shop.

public class AppActivity extends com.sdkbox.plugin.SDKBoxActivity 

In different phrases, leaving the code above is just not an possibility for us.

mPurchaseManager = new PurchaseManager(this); // is it potential to vary this file to make use of as listener not AppActivity class (object), however one thing else?

Are you saying you need to decrease adjustments to AppActivity?
Then you are able to do that by making PurcahaseManager a singleton.
If the intent of this query is to maintain the next code as defined earlier, it is unnecessary.

public class AppActivity extends com.sdkbox.plugin.SDKBoxActivity 

I’ve modified PurcahseManager to singleton in my newest code.

Hello @bluewind00 ,

Thanks in your nice job. You have got saved my undertaking

For individuals who get mingos::IAP to work by putting in the sport from Android Studio, nevertheless it crashes when you set up it from APK… DON’T FORGET TO ADD THESE LINES TO YOUR proguard-rules.professional:

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

simply replace just lately certainly one of my video games to billing library 4, with this pattern and it’s working nice.
the one odd factor, is that typically I get these crashes:

Crashed: Thread: SIGSEGV  0x0000000000000000
#00 computer 0x175f30  (std::__ndk1::__function::__func<Java_iap_PurchaseEventListener_onInitialized::$_1, std::__ndk1::allocator<Java_iap_PurchaseEventListener_onInitialized::$_1>, void ()>::operator()() [Java_iap_PurchaseEventListener.cpp:76])
#01 computer 0x40ec34 (cocos2d::Scheduler::replace(float) [functional:1867])
#02 computer 0x3f7d0c (cocos2d::Director::drawScene() [CCDirector.cpp:264])
#03 computer 0x3fa14c (cocos2d::Director::mainLoop() [CCDirector.cpp:1392])

line 76 is:

listener->onInitialized(success);

unsure if we must always add a strive catch there for the case of the listener not being current anymore…
or perhaps its one thing else. any concepts?

I’m very grateful in your generosity in releasing this code. Does anybody have any ideas on one of the simplest ways to utilize it inside a lua-based app?

I’m considering both hack the lua wrappers which might be provided with sdkbox, or create a substitute sdkbox:IAP class that calls into this new code the place potential and stubs something that isn’t supported. I’m uncertain what’s greatest although, so excited about what others with extra expertise with Android suppose.

Hmmm, I’m clearly not as good as I hoped I used to be! I’m struggling to know make use of this in an current cocos2d-x undertaking, of both sort – cpp or lua. I imagined if I stared on the directions for lengthy sufficient that it will turn out to be clear, nevertheless it’s not taking place. This appears to be a standalone pattern. So, is there a straightforward technique to decide precisely which information should be copied into an current undertaking and which information throughout the current undertaking want tweaking?

Sorry, ignore me: I can now see that extra detailed directions seem on this thread.