Playstore warning for using app permissions in manifest android

[venky9885]

Timeline
Now: Remove Photo and video permissions permission or submit declaration
If your use of Photo and video permissions is not permitted according to Google Play policy, you must remove it from your app. If your app has a legitimate reason for using Photo and video permissions, you must submit this declaration between now and the compliance deadline.

Playstore showing warning ,whether this package using this permissions ,if its using please remove in next release

[github-actions]

👋 @venky9885

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!

[pichillilorenzo]

No, there is no permission here: https://github.com/pichillilorenzo/flutter_inappwebview/blob/master/flutter_inappwebview_android/android/src/main/AndroidManifest.xml

check your own Android manifest.xml permissions or check other dependencies.

[venky9885]

ok Thanks

[github-actions]

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.