-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cordova-plugin-browsertab conflict with cordova android@7.1.3 and 7.1.4 #640
Comments
This is basically a manifestation of #508 and I do not expect we will fix it. It looks like [1] https://github.com/google/cordova-plugin-browsertab |
Hello Brody, https://www.youtube.com/watch?v=HKulxXDYJSs&feature=youtu.be I do not have the java background to maintain the plugin. So you say it is a bug in the plugin? The BrowserTab.gradle file which you reference says in the checkin comment, that it was a workaround regarding a gradle issue with cordova. To me it is not clear what would have to be done to fix the issue here. To my understanding, there seems to be something else wrong than the BrowserTab.gradle. As described previously, I have set the value in config.xml.
If this would have translated to gradle, than the code in BroswerTab.gradle should have had no effect. Best regards |
Workaround is given by @ashvinmay in google/cordova-plugin-browsertab#17 (comment), I just tested it myself:
I really hope someone will update and fix |
Hello Brody, Best regards, |
Thanks. As I said before I really hope someone will fix the problem in |
When you need the fix to be applied automatically the following hook will fix it for you: Add to config.xml:
create file: cordova/scripts/afterAddBrowserTabPlugin.js
|
Hello Icety, Best regards, |
The title says everything.
Replicate by creating a new project and adding
I get the following error. Maybe someone has an idea for a workaround. I tried setting the min version to 19 as mentioned in the error message. But without success.
This did not work:
Error message:
The text was updated successfully, but these errors were encountered: