-
-
Notifications
You must be signed in to change notification settings - Fork 535
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
Small update will be needed for proposed cordova-android patch release #759
Comments
You can now test with |
Thanks @brodybits - I'll revert the You don't mention it, but there was also this section that required change in our <source-file src="src/android/billing_key_param.xml" target-dir="res/values/" />
<config-file target="res/values/billing_key_param.xml" parent="/*">
<string name="billing_key_param">$BILLING_KEY</string>
</config-file> To this : <hook type="before_plugin_install" src="scripts/androidBeforeInstall.js" />
<config-file target="*/billing_key_param.xml" parent="/*">
<string name="billing_key_param">$BILLING_KEY</string>
</config-file> Where This should be covered by |
Good point. I would probably rewrite that section as follows: <source-file src="src/android/billing_key_param.xml" target-dir="res/values/" />
<config-file target="*/billing_key_param.xml" parent="/*">
<string name="billing_key_param">$BILLING_KEY</string>
</config-file> Old way to install And be sure to test on nightly and upcoming patch release of cordova-android. With nightly and upcoming patch release, the old TBH I have not dealt with the I hope this makes sense, please don't hesitate to ask in case of any questions or confusion. |
Sorry about this, I am having some second thoughts about the aidl change. Removing the second aidl entry from this plugin should be considered a breaking change since it would no longer work on cordova-android@7.1.1. And remapping of aidl on cordova-android should be considered a breaking change there since it causes the existing version of this plugin (v7.2.4) to install with an error. I have no idea how many other plugins may be using multiple aidl entries, as needed to support both cordova-android@6 and cordova-android@7. I think the right thing to do is to undo the aidl change on the proposed patch release and maybe master branch of cordova-android. More work on our side, but probably worth it if we can avoid more broken plugins in the near future. |
As for not breaking existing plugins. Maybe ignore More longer term, I wonder if a definite solution wouldn't be to support Example <aidl-file src="src/android/com/android/vending/billing/IInAppBillingService.aidl" target-dir="com/android/vending/billing" />
|
Idea 2. Remove the For plugins that have 2 entries, will it cause a problem if the aidl is installed twice at the same location? |
Yes that is the whole problem, unfortunately. It would be possible to use |
As discussed apache/cordova-android#547 I think we do want to keep the |
No problems, I understand the reasons for the confusion ;-) So I'll wait and the patch is released I ask users to stick to |
@j3k0 you have to get rid of the second |
Changes proposed in apache/cordova-android#555 were made so that the same
IInAppBillingService.aidl
entry in plugin.xml will work in cordova-android@6 and cordova-android@latest. This is achieved by remapping of target-dir if it does not start with "app". But this means that you will need to remove the secondIInAppBillingService.aidl
entry from plugin.xml and have your cordova-android@7 users upgrade to the upcoming cordova-android patch release.Right now you can test with the following cordova-android versions:
https://github.com/brodybits/cordova-android#7.1.3-patch-updates
cordova-android@nightly
(orhttps://github.com/apache/cordova-android#master
)Right now
https://github.com/j3k0/cordova-plugin-purchase#v7.1.0
(version before you added the extra aidl entry and hook script) will install and build with the proposed patch release as well as cordova-android@6. So it should be possible for you to get rid of the hook script as well.I hope this does not prove to be too much of a problem for you. If this does prove to be a major problem then I would be happy to look for another solution.
The text was updated successfully, but these errors were encountered: