Closed severinrudie closed 3 years ago
I do have one open question here. I'm not clear on what calling callback.onFailure is supposed to do. I didn't notice any difference in testing. If it's important, we could do a version check and only skip it on Android 11.
Maybe that's the more responsible thing to do anyway....
https://github.com/mozilla-lockwise/lockwise-android/issues/1219#issuecomment-727525094 Self-signed APK with the fix implemented for anyone willing to try and report bugs for that version.
Thank you for the reply and offering a solution. So, if I am reading correctly, this bug has been reported as far back as September and no official update of the app from Mozilla??
Thanks though and I may try the unsigned copy. When they do update through Google Play, will your copy update or do I have to uninstall and re-download from the Play Store? That would mean I'd have to keep an eye for updates on the store since your copy will not notify me in Play Store?
There is an official update that has been sent and is signed in the releases. https://github.com/mozilla-lockwise/lockwise-android/releases/tag/release-v4.0.3
It's simply not on the play store for the sole reason that Google updated their play store minimum required API and this is still not 100% up to date.
The app is working well and after the fix, I've been using it since it came out.
Oh OK, great! Thanks for the clarity.
Will this version I sideload see and update any future updates that appear in Play Store or will I have to uninstall and download the new version when I see one has been updated on the store?
TIA!
Will this version I sideload see and update any future updates that appear in Play Store or will I have to uninstall and download the new version when I see one has been updated on the store?
Fixes #1219
Testing and Review Notes
1219-fix-null-toast
LockwiseScreenshots or Videos
master
1219 fix
To Do