-
-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ionic v7 | Capacitor v5] This Plugin v13 is not working with Capacitor #1438
Comments
Hi @j3k0, can you please help me out here real quick? |
Nothing could be seen in the implementation. |
@Iamarslansaleem Have you solved this? |
I am using capacitor v5 (with Ionic v6, but prob the same for v7) for an iOS and Android app. It is working with plugin purchase v13 but the implementation needs a little modification, I found it here but it might help. Clearly the old InAppPurcharse2 does not work, so it needs to be removed. Import
Init :
I did a function to register everything and I call it when I need it. My code might not be perfect but it seems to work.
|
Observed behavior
Include logs with
store.verbosity = store.DEBUG
I can't provide the logs because It's not triggering it in Capacitor.
### Expected behavior
should work the same as version 13 working with Cordova.
### System Info
Output of
project info
.Ionic:
Ionic CLI : 7.1.1 (/usr/local/lib/node_modules/@ionic/cli)
Ionic Framework : @ionic/angular 7.1.2
@angular-devkit/build-angular : 16.1.4
@angular-devkit/schematics : 16.1.4
@angular/cli : 16.1.4
@ionic/angular-toolkit : 9.0.0
Capacitor:
Capacitor CLI : 5.1.1
@capacitor/android : 5.1.1
@capacitor/core : 5.1.1
@capacitor/ios : 5.1.1
Utility:
cordova-res : 0.15.4
native-run : 1.7.2
System:
NodeJS : v18.16.0 (/usr/local/bin/node)
npm : 9.7.2
OS : macOS Unknown
NOTE: Plugin version 13 is not triggering or not even responding with Capacitor. But version 11 works with Capacitor. Looking for help using In-App Purchase v13 with Capacitor v5. thanks!
you can see my implementation in the screenshot:
The text was updated successfully, but these errors were encountered: