Hi @Erel I am encountering a very strange issue. Recently we've updated all our sdks via the android sdk manager, we'v updated the last facebook jars/aars, updated firebase auth and the facebook auth libraries. We've began to target API 31 as it has become the latest requirement to submit to the play store. Prior to these updates we could call the FacebookSdk.SignIn() method and if the facebook app was installed, it would authenticate via the facebook app directly, and then fallback to the browser based login if the facebook app was not installed. Since our updates, calling the FacebookSdk.SignIn() always opens the browser to authenticate. After some research we discovered that someone was able to solve this issue by adding the QUERY_ALL_PACKAGES permissions to the manifest. This did solve our problem and enabled authentication again via the facebook app. However, after review by google, our application was rejected due to the use of the QUERY_ALL_PACKAGES permission is "not directly related to the core purpose of the app". So how can I make the FacebookSdk.SignIn() call authenticate via the facebook app without requiring the QUERY_ALL_PACKAGES permission.
When using PackageManager to list installed apps, only default OS apps are listed. This is a known restriction that affects targetSdkVersion>29 No effective way until now for listing apps. For ex, we have several CRM communications channel, one of them is WhatsApp integrated with WhatsApp...