#55 Error when clicking on file after an update

[Moueen BG]

Hello,

Thank you for a great application.
I get this error after an update. This also occured in previous versions.

I have attached a screen shot and included some description as overlying text.

After an update, the application gives an error if the file is clicked (blue rectangle).
One has to click the icon (blue circle) and select the file again to be able to open it; one
can then click the file normally until a new update.

This occurs only after an update.
The file is located on the external SD Card, LG G4 Dual Sim, H818P, Android 6.0 Software version V20h-AME-XX

[Jeff Harris]

Do you have the text of the error that is displayed? I can't reproduce the issue.

[Moueen BG]

Hello,

The error occurred again when I upgraded to the latest version 6.13.0 few
days ago. I could not take a screen shot. I presume one of the features of
the app.
I remember the error message was related to file access permissions.

I tried to track the error down.

1) Uninstalled version 6.13.0
2) Installed version 6.12.0 (I usually backup the apk files on external SD
Card using Total Commander; device not rooted)
3) PasswdSafe was opening files in external SD Card as read only.
Preferences > Files
unchecked "Legacy file chooser"

4) Opening the ".psafe3" file using the icon at 1 o'clock (i.e. the one
with the blue circle). Now the file can be edited (not read only).

5) Updated PasswdSafe to the latest version 6.13.0

6) The error is no longer there...

I was having the error with every update.The error seems to have been
resolved after I uninstalled and reinstalled the application.

Thank you again for a great software and for continuing to improve on it.

On Sat, Jan 6, 2018 at 7:45 PM, Jeff Harris jeffharris@users.sf.net wrote:

Do you have the text of the error that is displayed? I can't reproduce the
issue.

---

• [bugs:#55] https://sourceforge.net/p/passwdsafe/bugs/55/ Error when
  clicking on file after an update*

Status: open
Group: new
Labels: android error
Created: Sun Dec 24, 2017 12:29 PM UTC by Moueen BG
Last Updated: Sun Dec 24, 2017 12:29 PM UTC
Owner: nobody
Attachments:

• Password Safe_Android_Error after an update.png
  https://sourceforge.net/p/passwdsafe/bugs/55/attachment/Password%20Safe_Android_Error%20after%20an%20update.png
  (150.1 kB; image/png)

Hello,

Thank you for a great application.
I get this error after an update. This also occured in previous versions.

I have attached a screen shot and included some description as overlying
text.

After an update, the application gives an error if the file is clicked
(blue rectangle).
One has to click the icon (blue circle) and select the file again to be
able to open it; one
can then click the file normally until a new update.

This occurs only after an update.
The file is located on the external SD Card, LG G4 Dual Sim, H818P,
Android 6.0 Software version V20h-AME-XX

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/passwdsafe/bugs/55/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--

---

This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and contains legally privileged and/or
confidential information. If you are not the intended recipient of this
e-mail (or the person responsible for delivering this document to the
intended recipient), you are hereby notified that any dissemination,
distribution, printing or copying of this e-mail, and any attachments
thereto, is strictly prohibited. If you have received this e-mail in
error, please respond to the individual sending the message and notify
me, and permanently delete the original and any copy of any e-mail
and any printout thereof.

[Moueen BG]

The error seems to have resolved upon uninstallation and reinstallation of the app.
I can no longer reproduce it.
Unless you think otherwise the bug report can be closed.
Thank you again.

[Jeff Harris]

The reinstall probably cleared cached files and or permissions. Had you been able to capture a trace for the error message? I may be able to capture the error and at least not cause it to show if it is a normal occurrence.