github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-16 17:14:25 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android app force closes on start #182

New Issue
Closed
opened 2025-11-07 08:30:11 -06:00 by GiteaMirror · 37 comments
GiteaMirror commented 2025-11-07 08:30:11 -06:00
Owner
Copy Link

Originally created by @famewolf on GitHub (Jan 24, 2018).

Logcat attached. Device is a Leeco Le Pro 3. Error has occured on Omnirom, AICP and Paranoid Android for this device. (7.x Nougat) Fresh install. Using OpenGapps.

logcat.txt

Originally created by @famewolf on GitHub (Jan 24, 2018). Logcat attached. Device is a Leeco Le Pro 3. Error has occured on Omnirom, AICP and Paranoid Android for this device. (7.x Nougat) Fresh install. Using OpenGapps. [logcat.txt](https://github.com/bitwarden/mobile/files/1661498/logcat.txt)
GiteaMirror commented 2025-11-07 08:30:12 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 24, 2018):

01-23 23:01:06.816 11841 11841 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid ---> SimpleInjector.ActivationException: Key not yet valid ---> Java.Security.InvalidKeyException: Key not yet valid

Namely

Java.Security.InvalidKeyException: Key not yet valid

This is the error. For some reason that device doesn't work with the Android Keystore. Any idea why?

@kspearrin commented on GitHub (Jan 24, 2018): > 01-23 23:01:06.816 11841 11841 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid ---> SimpleInjector.ActivationException: Key not yet valid ---> Java.Security.InvalidKeyException: Key not yet valid Namely > Java.Security.InvalidKeyException: Key not yet valid This is the error. For some reason that device doesn't work with the Android Keystore. Any idea why?
GiteaMirror commented 2025-11-07 08:30:12 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 24, 2018):

Other than the fact it's a no name phone no idea. Ironically I got it to work one time then could never recreate it so I know it CAN be done but not what was different. Do we perhaps need different lines in build.prop to tell it a different device?

@famewolf commented on GitHub (Jan 24, 2018): Other than the fact it's a no name phone no idea. Ironically I got it to work one time then could never recreate it so I know it CAN be done but not what was different. Do we perhaps need different lines in build.prop to tell it a different device?
GiteaMirror commented 2025-11-07 08:30:12 -06:00
Author
Owner
Copy Link

@mzarglis commented on GitHub (Jan 24, 2018):

Same issue here.....really sucks as i use the mobile app a lot. same device leeco le pro 3

@mzarglis commented on GitHub (Jan 24, 2018): Same issue here.....really sucks as i use the mobile app a lot. same device leeco le pro 3
GiteaMirror commented 2025-11-07 08:30:12 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 24, 2018):

Which Rom are you on mzarglis? Factory?

@famewolf commented on GitHub (Jan 24, 2018): Which Rom are you on mzarglis? Factory?
GiteaMirror commented 2025-11-07 08:30:12 -06:00
Author
Owner
Copy Link

@mzarglis commented on GitHub (Jan 24, 2018):

AICP 13.1 (8.1.x)

@mzarglis commented on GitHub (Jan 24, 2018): AICP 13.1 (8.1.x)
GiteaMirror commented 2025-11-07 08:30:13 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 26, 2018):

I'm updating this because a user running the same rom was able to use the app...the two main differences were I was on opengapps mini and they were on opengapps stock. I also had magisk v15.3 installed. I flashed the same rom along with opengapps mini and it still crashed eliminating magisk. I'm now downloading opengapps "stock" to see if that resolves the issue.

@famewolf commented on GitHub (Jan 26, 2018): I'm updating this because a user running the same rom was able to use the app...the two main differences were I was on opengapps mini and they were on opengapps stock. I also had magisk v15.3 installed. I flashed the same rom along with opengapps mini and it still crashed eliminating magisk. I'm now downloading opengapps "stock" to see if that resolves the issue.
GiteaMirror commented 2025-11-07 08:30:13 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 26, 2018):

We've also seen this same problem on some older Samsung Devices (Galaxy S3 and S4). It's still known why those do not work with Android Keystore either, but I've found several cases documented online by others also confirming the problem.

@kspearrin commented on GitHub (Jan 26, 2018): We've also seen this same problem on some older Samsung Devices (Galaxy S3 and S4). It's still known why those do not work with Android Keystore either, but I've found several cases documented online by others also confirming the problem.
GiteaMirror commented 2025-11-07 08:30:13 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 26, 2018):

A clean install of AICP 12.1 rom (7.x) is able to install and run the bitwarden mobile app. It is the only rom I found that could do so among various I tried with both nougat and oreo bases. I have no idea what is significant.

@famewolf commented on GitHub (Jan 26, 2018): A clean install of AICP 12.1 rom (7.x) is able to install and run the bitwarden mobile app. It is the only rom I found that could do so among various I tried with both nougat and oreo bases. I have no idea what is significant.
GiteaMirror commented 2025-11-07 08:30:13 -06:00
Author
Owner
Copy Link

@mzarglis commented on GitHub (Jan 26, 2018):

yeah it worked for me on AICP 12.1 before i upgraded to 13.1

@mzarglis commented on GitHub (Jan 26, 2018): yeah it worked for me on AICP 12.1 before i upgraded to 13.1
GiteaMirror commented 2025-11-07 08:30:13 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 29, 2018):

I tried bitwarden on an Android Oreo Rom available for this device and got an identical abend. On the off chance it was a different error or explained better I've attached a logcat.txt from THAT rom.

logcat.txt

@famewolf commented on GitHub (Jan 29, 2018): I tried bitwarden on an Android Oreo Rom available for this device and got an identical abend. On the off chance it was a different error or explained better I've attached a logcat.txt from THAT rom. [logcat.txt](https://github.com/bitwarden/mobile/files/1672137/logcat.txt)
GiteaMirror commented 2025-11-07 08:30:14 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 29, 2018):

@famewolf It's the same exception with the Android Keystore.

@kspearrin commented on GitHub (Jan 29, 2018): @famewolf It's the same exception with the Android Keystore.
GiteaMirror commented 2025-11-07 08:30:14 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 29, 2018):

I've reported the issue to a couple of our Rom developers but not sure what priority it is with them since they don't use bitwarden. If I reflashed AICP 12.1 where it works is there anything I could do that would help identify whats different about it against the other 7 rom's I tried?

@famewolf commented on GitHub (Jan 29, 2018): I've reported the issue to a couple of our Rom developers but not sure what priority it is with them since they don't use bitwarden. If I reflashed AICP 12.1 where it works is there anything I could do that would help identify whats different about it against the other 7 rom's I tried?
GiteaMirror commented 2025-11-07 08:30:14 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 29, 2018):

Just share the above exception with them that occurs when trying to use the Android Keystore.

@kspearrin commented on GitHub (Jan 29, 2018): Just share the above exception with them that occurs when trying to use the Android Keystore.
GiteaMirror commented 2025-11-07 08:30:14 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 29, 2018):

I did and even linked to this ticket but most don't seem to consider it a high priority item since none of them use bitwarden and no other apps seem to have the same problem. For example lastpass works as expected. I appreciate all the time you took looking at this. Wish I could think of something to help resolve the issue.

@famewolf commented on GitHub (Jan 29, 2018): I did and even linked to this ticket but most don't seem to consider it a high priority item since none of them use bitwarden and no other apps seem to have the same problem. For example lastpass works as expected. I appreciate all the time you took looking at this. Wish I could think of something to help resolve the issue.
GiteaMirror commented 2025-11-07 08:30:15 -06:00
Author
Owner
Copy Link

@janos-szenfner commented on GitHub (Feb 20, 2018):

Same issue on Miui 9 with Android 7.0.

@janos-szenfner commented on GitHub (Feb 20, 2018): Same issue on Miui 9 with Android 7.0.
GiteaMirror commented 2025-11-07 08:30:15 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (Mar 3, 2018):

I'm experiencing this issue on a LeEco LePro 3 X727 with LineageOS 15.1 cleanly installed. Note: I do not install Google Play Services nor do I have any intention of doing so. FWIW, Bitwarden's mobile app worked just fine on the same phone with LineageOS 14.1 without Google Play Services.

@jaylittle commented on GitHub (Mar 3, 2018): I'm experiencing this issue on a LeEco LePro 3 X727 with LineageOS 15.1 cleanly installed. Note: I do not install Google Play Services nor do I have any intention of doing so. FWIW, Bitwarden's mobile app worked just fine on the same phone with LineageOS 14.1 without Google Play Services.
GiteaMirror commented 2025-11-07 08:30:15 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Mar 12, 2018):

I am on the 03/05 LeEco LePro 3 X727 with LineageOS 15.1 release which is the most recent official release. Bitwarden runs fine here so it does appear to be rom specific. I do have Google Play Services installed. (and did when I originally posted this issue)

@famewolf commented on GitHub (Mar 12, 2018): I am on the 03/05 LeEco LePro 3 X727 with LineageOS 15.1 release which is the most recent official release. Bitwarden runs fine here so it does appear to be rom specific. I do have Google Play Services installed. (and did when I originally posted this issue)
GiteaMirror commented 2025-11-07 08:30:16 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (Mar 12, 2018):

@famewolf We literally have the same setup except you have Google Play Services and I don't. Interesting. FWIW, Bitwarden still crashes on launch for me with the 3/5 build.

@jaylittle commented on GitHub (Mar 12, 2018): @famewolf We literally have the same setup except you have Google Play Services and I don't. Interesting. FWIW, Bitwarden still crashes on launch for me with the 3/5 build.
GiteaMirror commented 2025-11-07 08:30:16 -06:00
Author
Owner
Copy Link

@esaavedra89 commented on GitHub (May 25, 2018):

Some update of the issue or solution?

@esaavedra89 commented on GitHub (May 25, 2018): Some update of the issue or solution?
GiteaMirror commented 2025-11-07 08:30:16 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (May 25, 2018):

Still happening for me even with the latest APK of the Bitwarden App from APKPure.

@jaylittle commented on GitHub (May 25, 2018): Still happening for me even with the latest APK of the Bitwarden App from APKPure.
GiteaMirror commented 2025-11-07 08:30:16 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (May 26, 2018):

Not really much of an update but I switched to LineageOS 15.1 for the LeEco Le Pro 3 as well as opengapps mini and the issue went away. Opengapps mini was needed for google camera to work. Beangapps did NOT work so it's possible it also had something bitwarden needed. Might be worth testing. I eventually had settled on just using lastpass becuase of the hotkeys to use default form profile as well as ability to add credit cards and select which one to fill. Was "clumsier" in bitwarden. I'll re-evaluate farther down the line.

@famewolf commented on GitHub (May 26, 2018): Not really much of an update but I switched to LineageOS 15.1 for the LeEco Le Pro 3 as well as opengapps mini and the issue went away. Opengapps mini was needed for google camera to work. Beangapps did NOT work so it's possible it also had something bitwarden needed. Might be worth testing. I eventually had settled on just using lastpass becuase of the hotkeys to use default form profile as well as ability to add credit cards and select which one to fill. Was "clumsier" in bitwarden. I'll re-evaluate farther down the line.
GiteaMirror commented 2025-11-07 08:30:17 -06:00
Author
Owner
Copy Link

@mzarglis commented on GitHub (May 26, 2018):

The issue has been resolved for me as well since upgrading to AICP 13.1, now that i think of it i think i was using beangapps aswell and have since switched to opengapps.

But anyways no more force closes on my leeco le pro 3 on latest AICP 13.1 nightly with latest opengapps

@mzarglis commented on GitHub (May 26, 2018): The issue has been resolved for me as well since upgrading to AICP 13.1, now that i think of it i think i was using beangapps aswell and have since switched to opengapps. But anyways no more force closes on my leeco le pro 3 on latest AICP 13.1 nightly with latest opengapps
GiteaMirror commented 2025-11-07 08:30:17 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (May 26, 2018):

The Bitwarden Android app shouldn't require Google Play Services (opengapps) to be present on an Android device and it appears that based on the other posts in this thread, it now requires exactly that. This is a disturbing trend that I hope will be reversed in short order.

@jaylittle commented on GitHub (May 26, 2018): The Bitwarden Android app shouldn't require Google Play Services (opengapps) to be present on an Android device and it appears that based on the other posts in this thread, it now requires exactly that. This is a disturbing trend that I hope will be reversed in short order.
GiteaMirror commented 2025-11-07 08:30:17 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 26, 2018):

Play services is not required to run the app. We can run the app in a simulator without google apps and it works fine. There is also an f droid version if the app available in the releases page which doesn’t have any google play service libraries in it.

@kspearrin commented on GitHub (May 26, 2018): Play services is not required to run the app. We can run the app in a simulator without google apps and it works fine. There is also an f droid version if the app available in the releases page which doesn’t have any google play service libraries in it.
GiteaMirror commented 2025-11-07 08:30:17 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (May 29, 2018):

So I did some digging after looking at the code for this and stumbled upon this issue:

https://github.com/iamMehedi/Secured-Preference-Store/issues/15

It looks like somebody suggested removing the start and end dates from the keystore and somebody at the end confirmed that this resolved their very similar issue. I notice the bitwarden code seems to be setting both of them. Might this change be worth a shot?

@jaylittle commented on GitHub (May 29, 2018): So I did some digging after looking at the code for this and stumbled upon this issue: https://github.com/iamMehedi/Secured-Preference-Store/issues/15 It looks like somebody suggested removing the start and end dates from the keystore and somebody at the end confirmed that this resolved their very similar issue. I notice the bitwarden code seems to be setting both of them. Might this change be worth a shot?
GiteaMirror commented 2025-11-07 08:30:18 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (May 29, 2018):

Also, I found the PR that was merged to deal with the issue on their end. Looks like a pretty simple set of changes... I'd do it myself, but I don't have a proper build environment setup (Windows + Visual Studio) to do and test the work myself.

https://github.com/iamMehedi/Secured-Preference-Store/pull/27

@jaylittle commented on GitHub (May 29, 2018): Also, I found the PR that was merged to deal with the issue on their end. Looks like a pretty simple set of changes... I'd do it myself, but I don't have a proper build environment setup (Windows + Visual Studio) to do and test the work myself. https://github.com/iamMehedi/Secured-Preference-Store/pull/27
GiteaMirror commented 2025-11-07 08:30:18 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 29, 2018):

I created a build them them removed: 14d1d132a3

Our CI system is having issues at the moment so I can't provide a apk yet. Will be available here when that starts working: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

@kspearrin commented on GitHub (May 29, 2018): I created a build them them removed: https://github.com/bitwarden/mobile/commit/14d1d132a3b7622573af21793916ac2df9b537d7 Our CI system is having issues at the moment so I can't provide a apk yet. Will be available here when that starts working: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts
GiteaMirror commented 2025-11-07 08:30:18 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 31, 2018):

@jaylittle You can try the apk here now: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

@kspearrin commented on GitHub (May 31, 2018): @jaylittle You can try the apk here now: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts
GiteaMirror commented 2025-11-07 08:30:18 -06:00
Author
Owner
Copy Link

@jaylittle commented on GitHub (May 31, 2018):

Wow. That worked. Using that fdroid apk, I was finally able to actually use BitWarden on my LeEco LePro 3 phone with Lineage OS 15.1 sans Google Play Services for the very first time. Thank you! Hopefully others in this thread can confirm this fix as well and experience some relief.

@jaylittle commented on GitHub (May 31, 2018): Wow. That worked. Using that fdroid apk, I was finally able to actually use BitWarden on my LeEco LePro 3 phone with Lineage OS 15.1 sans Google Play Services for the very first time. Thank you! Hopefully others in this thread can confirm this fix as well and experience some relief.
GiteaMirror commented 2025-11-07 08:30:18 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jun 4, 2018):

This is pushed to the latest play store beta. Will go out in the next version.

@kspearrin commented on GitHub (Jun 4, 2018): This is pushed to the latest play store beta. Will go out in the next version.
GiteaMirror commented 2025-11-07 08:30:19 -06:00
Author
Owner
Copy Link

@SamuelGeiger commented on GitHub (Jun 27, 2018):

This issue is not resolved. I try to use the app on a Sony xperia z1 with the latest stock rom and it crashes every time on Startup. I don't have my phone rooted so I don't now how to obtain any logs. I did send two crash reports.

@SamuelGeiger commented on GitHub (Jun 27, 2018): This issue is not resolved. I try to use the app on a Sony xperia z1 with the latest stock rom and it crashes every time on Startup. I don't have my phone rooted so I don't now how to obtain any logs. I did send two crash reports.
GiteaMirror commented 2025-11-07 08:30:19 -06:00
Author
Owner
Copy Link

@mjarsenault commented on GitHub (Jan 16, 2019):

Has there been a fix for this yet? I'm on a Le Eco Pro 3 with the latest AICP 14.0 ROM installed, and Bitwarden wont even open.

I'd really love to use it but won't be able to without it working on my phone!

@mjarsenault commented on GitHub (Jan 16, 2019): Has there been a fix for this yet? I'm on a Le Eco Pro 3 with the latest AICP 14.0 ROM installed, and Bitwarden wont even open. I'd really love to use it but won't be able to without it working on my phone!
GiteaMirror commented 2025-11-07 08:30:19 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 16, 2019):

@mjarsenault Do you have at logs available from the phone?

@kspearrin commented on GitHub (Jan 16, 2019): @mjarsenault Do you have at logs available from the phone?
GiteaMirror commented 2025-11-07 08:30:19 -06:00
Author
Owner
Copy Link

@mjarsenault commented on GitHub (Jan 16, 2019):

@mjarsenault Do you have at logs available from the phone?

(I hope I did this right)

01-16 08:33:25.133 935 1059 I ActivityManager: Start proc 
21724:com.x8bit.bitwarden/u0a175 for activity 
com.x8bit.bitwarden/md5b95ad25b85f158431f24aa9fc17a1c1e.SplashActivity
01-16 08:33:27.348 21724 21724 E AndroidRuntime: FATAL EXCEPTION: main
01-16 08:33:27.348 21724 21724 E AndroidRuntime: Process: 
com.x8bit.bitwarden, PID: 21724
01-16 08:33:27.348 21724 21724 E AndroidRuntime: 
android.runtime.JavaProxyThrowable: 
System.Reflection.TargetInvocationException: Exception has been thrown by 
the target of an invocation. ---> System.InvalidOperationException: The 
configuration is invalid. Creating the instance for type 
ISecureStorageService failed. Key not yet valid ---> 
SimpleInjector.ActivationException: Key not yet valid ---> 
Java.Security.InvalidKeyException: Key not yet valid
@mjarsenault commented on GitHub (Jan 16, 2019): > @mjarsenault Do you have at logs available from the phone? (I hope I did this right) ``` 01-16 08:33:25.133 935 1059 I ActivityManager: Start proc 21724:com.x8bit.bitwarden/u0a175 for activity com.x8bit.bitwarden/md5b95ad25b85f158431f24aa9fc17a1c1e.SplashActivity 01-16 08:33:27.348 21724 21724 E AndroidRuntime: FATAL EXCEPTION: main 01-16 08:33:27.348 21724 21724 E AndroidRuntime: Process: com.x8bit.bitwarden, PID: 21724 01-16 08:33:27.348 21724 21724 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid ---> SimpleInjector.ActivationException: Key not yet valid ---> Java.Security.InvalidKeyException: Key not yet valid ```
GiteaMirror commented 2025-11-07 08:30:20 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 16, 2019):

On the Leeco Pro 3, the problem appears to be some of the Rom's available. For example Lineage 15.1 does not give the error nor does the latest AICP as far as I know. You seem to be on an older version? Try one of the ones with Oreo or Pie and the problem should go away. I personally run Lineage 15.1 (and am looking at Lineage 16..given you'll have to do a clean install to jump a version you might as well go all the way to pie) on my LeEco Pro 3.

@famewolf commented on GitHub (Jan 16, 2019): On the Leeco Pro 3, the problem appears to be some of the Rom's available. For example Lineage 15.1 does not give the error nor does the latest AICP as far as I know. You seem to be on an older version? Try one of the ones with Oreo or Pie and the problem should go away. I personally run Lineage 15.1 (and am looking at Lineage 16..given you'll have to do a clean install to jump a version you might as well go all the way to pie) on my LeEco Pro 3.
GiteaMirror commented 2025-11-07 08:30:20 -06:00
Author
Owner
Copy Link

@mjarsenault commented on GitHub (Jan 16, 2019):

I'm on the January 10th (latest) release of AICP 14.0, which is a Pie ROM.

@mjarsenault commented on GitHub (Jan 16, 2019): I'm on the January 10th (latest) release of AICP 14.0, which is a Pie ROM.
GiteaMirror commented 2025-11-07 08:30:20 -06:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Jan 16, 2019):

I'm on the January 10th (latest) release of AICP 14.0, which is a Pie ROM.

Interesting. Well obviously something has changed then because I recall reading earlier users on AICP saying it was working at the time...perhaps it worked on AICP Oreo and doesn't work on pie. Perhaps you can point out the issue to the rom developer and indicate the app DOES work on Lineage15.1. It's possible he can find out what the issue is. I would also perhaps try a couple of different gapps versions (I'm on opengapps mini).

Realistically there is not much the bitwarden guys can do since on factory rom's the app will work as it should and the problem appears to be specific to custom roms/versions. (sadly ALL our rom's are considered custom since the manufacturer abandoned support back when it was on marshmallow..it's still a heck of a device and the price for me was hard to beat)

@famewolf commented on GitHub (Jan 16, 2019): > I'm on the January 10th (latest) release of AICP 14.0, which is a Pie ROM. Interesting. Well obviously something has changed then because I recall reading earlier users on AICP saying it was working at the time...perhaps it worked on AICP Oreo and doesn't work on pie. Perhaps you can point out the issue to the rom developer and indicate the app DOES work on Lineage15.1. It's possible he can find out what the issue is. I would also perhaps try a couple of different gapps versions (I'm on opengapps mini). Realistically there is not much the bitwarden guys can do since on factory rom's the app will work as it should and the problem appears to be specific to custom roms/versions. (sadly ALL our rom's are considered custom since the manufacturer abandoned support back when it was on marshmallow..it's still a heck of a device and the price for me was hard to beat)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#182
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?