There are two common Facebook login methods: NativeApp, which communicates with the installed Facebook app and authenticates an app with the same account used by the Facebook app, and CustomTab, which uses the installed Chrome browser to show the Facebook login page within an app.
This is why by default App Cloner automatically enables the WebView login method (see cloning option Facebook login). This login method shows the Facebook login page in a web view component inside the cloned app. The web view session cookies are stored locally within the cloned app, meaning you can easily use different Facebook accounts when logging into different cloned apps.
In October, 2021 Facebook deprecated the WebView login method for Android apps (see https://developers.facebook.com/docs/facebook-login/android/deprecating-webviews) but if you have the premium subscription of App Cloner you may continue to use the WebView login method.
However, lately we’re seeing that apps do not ship with the necessary code to be able to use the WebView login method. For example, recent versions of LINE only include implementations of the CustomTab login method. This means it’s impossible for the cloned apps to redirect the default login methods to the WebView login method.
A solution is to use the Change app references cloning option, which is available since App Cloner 2.15.
First, you need to create clones of Chrome. For each clone of your app you need to create a clone of Chrome, e.g. LINE 1 > Chrome 1, LINE 2 > Chrome 2, LINE 3 > Chrome 3, etc. Make sure you open all the Chrome clones at least once.
Then you create clones of your desired app and enable the cloning option Change app references, enabling the Chrome app. Once installed, each clone points to its own Chrome browser instance with its individual cookie settings and you may log in using a different Facebook account with each clone.
App Cloner 2.16 improves the Change app references cloning option, allowing you to limit the redirection of app references.
By setting this value to 1 you can make all clones to point to the first Chrome clone. You can then create a single Chrome clone and enable the privacy option Incognito mode and select Automatic (when leaving app). This option clears all the app data, including Facebook session cookies, when exiting the cloned app. This way, you can use a single Chrome clone instance to handle Facebook logins for all cloned apps, which significantly reduces storage requirements.
IMPORTANT: You must make sure to force stop or swipe away the cloned app after returning from the Facebook login before attempting a new Facebook login from another clone. Otherwise the cloned Chrome instance will continue to run in the background and won’t delete its app data.