Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Syncing, Exiting or Searching Firefox Lockwise (Android) Yields "java.lang.IllegalArgumentException: NetworkCallback was already unregistered"

  • 1 reply
  • 1 has this problem
  • 75 views
  • Last reply by bmgthewiz

more options

To reproduce, unlock your AT&T Galaxy S8+ running Android 9 & have Firefox Lockwise connected to your device. Then, perform the following:

  1. Open Lockwise through the app drawer
  2. Try searching for a credential and hit the back button
  3. Hit the back button again to exit the app
  4. Witness crash of "java.lang.IllegalArgumentException: NetworkCallback was already unregistered"

Also can occur during syncs, too.

To reproduce, unlock your AT&T Galaxy S8+ running Android 9 & have Firefox Lockwise connected to your device. Then, perform the following: # Open Lockwise through the app drawer # Try searching for a credential and hit the back button # Hit the back button again to exit the app # Witness crash of "java.lang.IllegalArgumentException: NetworkCallback was already unregistered" Also can occur during syncs, too.
Attached screenshots

Chosen solution

PARTIALLY RESOLVED: These actions may have resolved the password syncing issue, but after reading about issues with key3.db and key4.db I performed the following and it seems to work now:

  1. Navigated to about:config and enabled signon.management.page.fileImport.enabled
  2. Clicked on Help > More Troubleshooting Information... > Open Profile folder
  3. Exported passwords to a CSV file with "Export to File" option in Logins & Passwords
  4. Removed all passwords
  5. Shutdown FF
  6. Renamed the DB files above to *.OLD extension
  7. Started up FF and the key4.db file was recreated. Logged in to sync across devices.
  8. Opened logins and clicked on Import From File to import the CSV file that was generated.
  9. Passwords that weren't duplicates or had errors were imported. After refreshing the Lockwise Android App, the new passwords are there.

It's under observation to see if new passwords have any problems, and the app still crashes a TON (unfortunately), but at least my new passwords are showing.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

PARTIALLY RESOLVED: These actions may have resolved the password syncing issue, but after reading about issues with key3.db and key4.db I performed the following and it seems to work now:

  1. Navigated to about:config and enabled signon.management.page.fileImport.enabled
  2. Clicked on Help > More Troubleshooting Information... > Open Profile folder
  3. Exported passwords to a CSV file with "Export to File" option in Logins & Passwords
  4. Removed all passwords
  5. Shutdown FF
  6. Renamed the DB files above to *.OLD extension
  7. Started up FF and the key4.db file was recreated. Logged in to sync across devices.
  8. Opened logins and clicked on Import From File to import the CSV file that was generated.
  9. Passwords that weren't duplicates or had errors were imported. After refreshing the Lockwise Android App, the new passwords are there.

It's under observation to see if new passwords have any problems, and the app still crashes a TON (unfortunately), but at least my new passwords are showing.

Modified by bmgthewiz