Crash when trying to use autofill while Lockwise is locked. #1076
Comments
|
Hello @Fighter1000 thank you for this report! Can you please mention the Lockwise version you are using?
Looking forward to hearing an answer from you. Regards, |
The version shown in the Lockwise settings is 3.1.0 (5362)
It crashes even before asking for my fingerprint, so no. Thanks for trying to help out. Edit: md |
|
Thanks for the answer! Regards, |
Tried that multiple times already, the issue still remained. |
|
Is your phone rooted? |
I am also experiencing these crashes. Lockwise v3.1.0 I experience a crash after tapping 'Unlock Firefox Lockwise' with fingerprint unlock enabled or disabled. I also experience a crash when Lockwise is unlocked and I tap 'Search Firefox Lockwise'. Phone is not rooted. |
|
@Fighter1000 @RocketCoach thanks for the help! @eliserichards @jhugman @changecourse I was able to reproduce this but it is under very specific steps and not really a normal user behavior for more details please check the following:Steps:
--------- beginning of crash
2019-11-21 15:47:01.586 29421-29421/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: mozilla.lockbox, PID: 29421
java.lang.RuntimeException: Unable to start activity ComponentInfo{mozilla.lockbox/mozilla.lockbox.view.AutofillRootActivity}: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2955)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Caused by: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
at android.app.Activity.onCreate(Activity.java:1038)
at l.h.c.c.onCreate(ComponentActivity.java:1)
at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:1)
at l.l.d.d.onCreate(FragmentActivity.java:22)
at l.b.k.i.onCreate(AppCompatActivity.java:4)
at mozilla.lockbox.view.AutofillRootActivity.onCreate(AutofillRootActivity.kt:1)
at android.app.Activity.performCreate(Activity.java:7183)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
2019-11-21 15:47:01.588 29421-29421/? D/n.b.f.b.a.a: Proguard UUIDs file not found.
2019-11-21 15:47:01.590 6151-23709/? I/DiscoveryManager: Filter criteria(null) scannerFlags(0)
2019-11-21 15:47:01.591 29817-29817/? D/ViewRootImpl@809e60e[BrowserApp]: MSG_WINDOW_FOCUS_CHANGED 0
2019-11-21 15:47:01.594 4773-8180/? D/GameManagerService: identifyGamePackage. mozilla.lockbox
2019-11-21 15:47:01.594 4773-8180/? D/GamePkgDataHelper: getGamePkgData(). mozilla.lockbox
2019-11-21 15:47:01.594 4773-8180/? D/GameManagerService: identifyGamePackage. mozilla.lockbox
2019-11-21 15:47:01.595 4773-8180/? D/GamePkgDataHelper: getGamePkgData(). mozilla.lockbox
2019-11-21 15:47:01.595 4773-6244/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.595 4773-5605/? D/ConnectivityService: filterNetworkStateForUid() uid: 10033 networkInfo: [type: WIFI[] - WIFI, state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Bf5971b", failover: false, available: true, roaming: false, metered: false]
2019-11-21 15:47:01.595 4773-8180/? D/GameManagerService: identifyGamePackage. mozilla.lockbox
2019-11-21 15:47:01.595 4773-8180/? D/GamePkgDataHelper: getGamePkgData(). mozilla.lockbox
2019-11-21 15:47:01.596 4773-6244/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.596 6151-23709/? W/GuestModeDeviceProber: setFilterCriteria
2019-11-21 15:47:01.597 4773-6244/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.598 4773-5605/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.599 4773-5605/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.599 4773-6244/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.600 4773-6244/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.602 4773-5605/? W/StorageManager: getStorageLowBytes lowPercent : 5, lowBytes : 2821057740, maxLowBytes : 524288000
2019-11-21 15:47:01.602 4773-6244/? D/ConnectivityService: filterNetworkStateForUid() uid: 10628 networkInfo: [type: WIFI[] - WIFI, state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Bf5971b", failover: false, available: true, roaming: false, metered: false]
2019-11-21 15:47:01.603 4244-4244/? I/android.hardware.wifi@1.0-service: installApfPacketFilter
2019-11-21 15:47:01.603 4244-4244/? D/WifiHAL: Setting APF program, halHandle = 0x72be662240
2019-11-21 15:47:01.603 4244-4244/? I/WifiHAL: createRequest: APF set program request
2019-11-21 15:47:01.605 4244-4244/? I/WifiHAL: Done!
2019-11-21 15:47:01.610 29421-29446/? I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
2019-11-21 15:47:01.610 29421-29446/? I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
2019-11-21 15:47:01.612 4406-4606/? D/DnsProxyListener: DNSDBG::dns addrinfo af 2
2019-11-21 15:47:01.613 4406-4606/? D/DnsProxyListener: DNSDBG::dns by addr af 2
2019-11-21 15:47:01.621 4773-4911/? I/WindowManager: Destroying surface Surface(name=PopupWindow:56320a1) called by com.android.server.wm.WindowStateAnimator.destroySurface:2465 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:967 com.android.server.wm.WindowState.destroyOrSaveSurfaceUnchecked:3661 com.android.server.wm.WindowState.destroySurface:3609 com.android.server.wm.WindowState.destroySurface:3591 com.android.server.wm.AppWindowToken.destroySurfaces:722 com.android.server.wm.AppWindowToken.destroySurfaces:706 com.android.server.wm.WindowState.onExitAnimationDone:5302
2019-11-21 15:47:01.621 4256-4490/? I/SurfaceFlinger: id=403 Removed PopupWindow:56320a1#0 (3/12)
2019-11-21 15:47:01.623 29817-29817/? D/ViewRootImpl@809e60e[BrowserApp]: MSG_RESIZED: frame=Rect(0, 0 - 1440, 2960) ci=Rect(0, 84 - 0, 168) vi=Rect(0, 84 - 0, 168) or=1
2019-11-21 15:47:01.626 29421-29421/? W/System.err: SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
2019-11-21 15:47:01.626 29421-29421/? W/System.err: SLF4J: Defaulting to no-operation MDCAdapter implementation.
2019-11-21 15:47:01.626 29421-29421/? W/System.err: SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.
2019-11-21 15:47:01.627 29421-29984/? I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
2019-11-21 15:47:01.627 29421-29984/? I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
2019-11-21 15:47:01.627 4406-4606/? D/DnsProxyListener: DNSDBG::dns addrinfo af 2
2019-11-21 15:47:01.628 4256-4490/? I/SurfaceFlinger: id=403 Removed PopupWindow:56320a1#0 (-2/12)
2019-11-21 15:47:01.629 4773-6244/? D/Debug: !@DumpState : SHIP
2019-11-21 15:47:01.629 4773-6244/? D/Debug: !@DumpState : debug level:0x4f4c
2019-11-21 15:47:01.630 4773-6244/? D/Debug: !@Dumpstate : Finally, system will skip dumpstate
2019-11-21 15:47:01.630 4773-6244/? W/ActivityManager: crash : mozilla.lockbox,0
2019-11-21 15:47:01.630 4773-6244/? W/ActivityManager: Force finishing activity mozilla.lockbox/.view.AutofillRootActivity
2019-11-21 15:47:01.632 4773-6244/? W/ActivityManager: Force finishing activity org.mozilla.firefox/org.mozilla.gecko.BrowserApp
2019-11-21 15:47:01.633 4773-6244/? W/MultiScreenManagerService: moveTaskBackToDisplayIfNeeded(): root activity or app is null, task=TaskRecord{4ce26e9d0 #44 A=org.mozilla.firefox.BROWSER U=0 StackId=1 sz=2}, rootActivity=null
2019-11-21 15:47:01.637 4256-4256/? I/Layer: id=403 onRemoved PopupWindow:56320a1#0
2019-11-21 15:47:01.638 4773-6244/? W/ActivityManager: Force finishing activity mozilla.lockbox/.view.RootActivity |
No, I don't even have developer mode enabled.
No, it still crashes when trying to search Lockwise, even if the phone security is completely disabled. |
That doesn't seem like the issue I had. I tested it in Instagram and I didn't use multitasking. |
|
@Fighter1000 Your bug is regarding Lockwise being locked. So I added those steps so we can reproduce it faster and don't wait a few minutes until the app is locked. Thanks, |
|
I'm affected by this as well. On Android 8.0.0 and Lockwise 3.2.0, tapping the 'Unlock' or 'Search' prompts in Firefox causes Lockwise to crash. I've sent a couple of feedback reports after the app crashes. Here's a summary of what I submitted: System information
Stack traceNetwork
Application data
|
|
I have the same issue (it crash when using autofill for user or password. Any applications, each time). The application used to work. Phone: Samsung s7
Same issue I tried to unlock directly in lockwise then use autoswitch -> same issue. |
|
I am having exactly the same issue with an Asus Zenfone 3 (ZE552KL). As previous posts suggest, my phone has Android 8.0.0 on it. |
|
I'm having the same problem as Fighter1000: Lockwise 3.2.0 crashes as soon as I touch the Lockwise prompt to fill in credentials. Worked initially for a Lockwise update or two, but hasn't since one of the latest updates got applied about a month or two back. I'm on a VZW issued Samsung GS7 (SM-G930V), Android 8.0.0, with lastest VZW updates applied. |
|
I have same issue. And I also use a device running Android 8.0. Device and App Information
Besides, I test some different versions of Lockwise. Hope this can help you figure out what makes the Lockwise crash. |
|
I have the exact same problem on my S7. Only difference is that I unlock my mobile using a device pattern not with a fingeprint. It also used to work, but I haven't tracked the precise version when it stopped working. I love Lockwise, please fix this bug.. |
|
Same issue on Sony Xperia X Performance. Again Android 8.0.0. |
|
Same issue here on my Samsung Galaxy A5 2017 with Android 8.0.0. |
|
@abodea To confirm:
...and if you upgrade at all, this crash goes away? |
|
Hello, @ddurst I only have 8.1.0 as the next version of android available. |
|
Hi, I have exactly the same issue, also Samsung Galaxy S7 - Android 8.0.0 - not rooted - with fingerprint. Unfortunately, I don't expect Samsung will upgrade Android for older phones... :/ Lockwise version 3.3.0 (5784) |
|
I confirmed this evening that 3.1.0 (Build 5362) is the last version to work with my Android 8.0.0 phone (Samsung GS7 from VZW). 3.2.0 and above crash. For those of us with phones locked by cellular carriers, we can't upgrade to a newer version of Android until the carrier issues it, and I'm assuming in most cases they have no intention of doing so. |
|
I have the same problem with AT&T S7 running 8.0.0. Crashes as soon as I click on the Unlock with Lockwise button. Anytime I switch to lockwise from another app, using the redirect button is when it happens. For the most part I can launch the app and search my users and passwords just fine. Edit: I have found that I can launch the app, log in with my fingerprint then switch back to the auto fill and it will work. But trying to launch the app from another app is the problem for me. |
|
Same problem. |
|
Is there any way a bystander can help with the 'needs-reproduce' status of this? I thought @abodea had already provided a repro? |
|
You're right @wryun, we have some good STR now. I will remove the "needs-reproduce" tag 😄 |
|
It's still happening for me: SM-G930F (Samsung Galaxy S7) |
|
Same issue: Unfortunately no androids updates from the manufacturer are expected to arrive |
|
Lockwise 4.0 still crashes with Android 8.0.0. There doesn't seem to be any effort to solve this issue, so I'm giving up on Lockwise. Uninstalled. |
|
The last commit is on February 18. This is starting to look like abandonware. What's going on at Mozilla? |
|
I've noticed that Firefox Preview (Fenix) has added password support, so now it and Lockwise can fight about who's saving passwords. Seems like they might have decided to go for that rather than a separate app. |
Would this be able to fill in mobile app passwords, like Lockwise (did)? If so, combining the two would make sense. Would be nice of Mozilla to communicate this, however. |
…galStateException in autofill activity It seems that in Android 8.0.0 (API 26) there is a bug where setting the auto fill activity window to translucent causes an exception to be thrown. Per mozilla-lockwise#1076 it doesn't happen on Android 8.1. This patch works around the problem by not setting the window to be translucent on API 26 only. The window is (obviously) not translucent, but the App doesn't crash and is otherwise usable.
…galStateException in autofill activity It seems that in Android 8.0.0 (API 26) there is a bug where setting the auto fill activity window to translucent causes an exception to be thrown. Per mozilla-lockwise#1076 it doesn't happen on Android 8.1. This patch works around the problem by not setting the window to be translucent on API 26 only. The window is (obviously) not translucent, but the App doesn't crash and is otherwise usable.
…galStateException in autofill activity It seems that in Android 8.0.0 (API 26) there is a bug where setting the auto fill activity window to translucent causes an exception to be thrown. Per mozilla-lockwise#1076 it doesn't happen on Android 8.1. This patch works around the problem by not setting the window to be translucent on API 26 only. The window is (obviously) not translucent, but the App doesn't crash and is otherwise usable.
|
it's AUG 2021and i'm still having the same problem. When i try to autofill the app crashes. |
Steps to reproduce
Lock Lockwise (fingerprint is enabled)
Try to log into any app using autofill.
Tap "Unlock Lockwise"
Expected behavior
Lockwise can be unlocked with the fingerprint, after which I can log on with the app's password.
Actual behavior
Lockwise crashes with "Firefox Lockwise stopped"
Device & build information
The text was updated successfully, but these errors were encountered: