Use of Use of the broad package (App) visibility (QUERY_ALL_PACKAGES) permission being restricted by Google

[jcassidyav]

Google are restricting the use of QUERY_ALL_PACKAGES in apps from this year.

See: https://support.google.com/googleplay/android-developer/answer/10158779?hl=en#zippy=%2Cpermitted-uses-of-the-query-all-packages-permission%2Cexceptions%2Cinvalid-uses

Our app has been flagged in the store as having this permission set, and we traced it back to inappbrowser.

i.e. in the AndroidManifest.xml file.

I built the plugin locally removing this line and it appears to work correctly for the demo and my simple scenarios on api 30/32 emulators, is this required for different scenarios, or have i missed something in my testing?

[jdnichollsc]

Hello mate, thanks for asking

I'm planning to publish a new version soon removing that, let me confirm you!

Best Regards,
Juan

[jcassidyav]

That's fantastic! Thank you.

[edusperoni]

Hello!

Any updates on this?

I'll gladly open a PR to fix this, but I'm not sure if there are any other changes needed

[eestevez123]

Hey guys! I also work on an app that uses this package and it has been flagged by the Play Store for using this permission. Any updates as to when the PR would merge and a new version would release? Thank you!

[tommag21]

Hi everyone, I am in dire need of a fix for this issue and found this fork by farfromrefuge, who maintains a lot of NativeScript plugins. It includes the fix for this issue plus some minor optimization. The author can merge it into master.

[jdnichollsc]

Hello folks, I'm planning to publish a new version today with new options, thank you for your patience!

[jdnichollsc]

@tommag21 what optimizations are you referring to? 🤔

[jdnichollsc]

Hi everyone, I am in dire need of a fix for this issue and found this fork by farfromrefuge, who maintains a lot of NativeScript plugins. It includes the fix for this issue plus some minor optimization. The author can merge it into master.

I remember I closed his PR because he wasn't very willing to have a simple discussion from a new issue before making changes to the repository, which is very important when working in a community :)

[tommag21]

@tommag21 what optimizations are you referring to? 🤔

I don't know, just based on the commits' name.

I remember I closed his PR because he wasn't very willing to have a simple discussion from a new issue before making changes to the repository, which is very important when working in a community :)

I'm sorry, I did not know that.

[woeckener]

Hey guys, just wanted to ask respectfully, if there is still work being done here or if and when we can count on a new version. Thank you!

[dannyknowlton]

Hello folks, I'm planning to publish a new version today with new options, thank you for your patience!

Hi @jdnichollsc, how's it going with this update?

[jdnichollsc]

Hello folks, excuse me for the delay
My Mac stopped working, I'm planning to release a new version as soon as possible, sorry for the inconvenience 🙏

Regards,
Juan

[alexxxo1985]

Any updates on this? @jdnichollsc

[kandangit]

Hello, We also have the issue and need a fix in the short term , before July 20th. For now we will resort to having an external browser opening the URL and removing the plugin dependency.
Many thanks.