flutter_inappwebview
flutter_inappwebview copied to clipboard
pichillilorenzo
[Question] Android 15 disable `getDatabaseEnabled` method
The following description of Android 15 says that getDatabaseEnabled, which this plugin uses, will become unavailable within 12 months.
Does that mean that if this plugin is not fixed, webviews that use it will stop working within 12 months?
https://developer.android.com/about/versions/15/deprecations?hl=ja#websql-webview
👋 @ShuheiSuzuki-07
NOTE: This comment is auto-generated.
Are you sure you have already searched for the same problem?
Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!
If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.
In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.
Following these steps can save you, me, and other people a lot of time, thanks!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
English ref: https://developer.android.com/about/versions/15/deprecations?hl=en#websql-webview
They will not remove the method, it will be just a method no-op, that means it will do nothing.
These methods will become a no-op on all Android versions in the next 12 months.
You won’t have build errors or whatever.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.