Deleted account auto logging in after uninstalling and reinstalling the jami android app

Describe your environment

MacBook Air M2

Android Studio Jellyfish | 2023.3.1 Patch 1 Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Please specify the following:

• Jami version: 20240506-01
• Device model: Pixel 7a
• Android version: 14
• What build you are using: your own (commit id = 04117d84 + daemon commit id = aa24a6db)]

Steps to reproduce

• Can you reproduce the bug: [occasionally]
• Steps:
  1. Build and Install the app from Android Studio
  2. Create new account and sign in (e.g User A)
  3. Uninstall the app
  4. Build and Install the app again from Android Studio
  5. App launches but in logged-in state with User A, even if you deleted the account before uninstalling the app.
• Actual result: App is auto-logging in with deleted/previous user
• Expected result: App should never auto-login with deleted/previous user

After reproducing the issue, i looked into the cache directory using device explorer. A file named ns.jami.net is automatically created inside a directory /namecache. This file contains the same username which was deleted in previous installation. I don't know from where this file is being generated automatically after fresh installation.

Screenshot of Device Explorer https://ibb.co/6bSFMjN

sign-in/login doesn't exist for Jami, the account is generated locally (except if it's a JAMS account or a SIP account)

If you delete your account, the account doesn't exist anywhere.

My guess is that for 3. you uninstall the app and keep the data (it's an option on the pixel). It's the only way possible.

The file for ns.jami.net is the cache of mapping username<->uri, so if you lookup for a contact, this will be stored there but nothing related.

Ok i will try to add allowBackup=false in the manifest. Maybe that would fix the issue. The strange this thing is that it only brings back the very first account which was created on the device, not any other account which were created and then deleted afterward.

I can see this bug sometimes too.

Uninstall without keeping data is done by the device. If the app data is still there at re-install, I think it is not on us.

However, you were talking about allowBackup=false and I just read this https://stackoverflow.com/questions/59210718/how-to-force-delete-application-data-on-uninstall-android. Need to dig ...

Fixed this issue by disabling the backup flags in manifest

android:allowBackup="false"

android:fullBackupContent="false"

tools:replace="android:allowBackup"

android:dataExtractionRules="@xml/data_extraction_rules"

Create a file data_extraction_rules.xml in /res/values/xml directory and add this content

<?xml version="1.0" encoding="utf-8"?> <data-extraction-rules> <cloud-backup> <exclude domain="root" /> <exclude domain="file" /> <exclude domain="database" /> <exclude domain="sharedpref" /> <exclude domain="external" /> </cloud-backup> <device-transfer> <exclude domain="root" /> <exclude domain="file" /> <exclude domain="database" /> <exclude domain="sharedpref" /> <exclude domain="external" /> </device-transfer> </data-extraction-rules>

Reference: https://stackoverflow.com/questions/70365809/how-to-specify-to-not-allow-any-data-backup-with-androiddataextractionrules

https://stackoverflow.com/questions/59210718/how-to-force-delete-application-data-on-uninstall-android

Would you mind to do a commit and push it on our gerrit for review please? I can help you to setup if needed ? Thanks,

Yeah sure. Please help me setting it up.

https://docs.jami.net/en_US/developer/new-developers/working-with-gerrit.html can help

Try this and tell me if you need more help.

added bug label