4.5.2 crashing on iPhone

Problems with KyPass on iPhone should be reported in here
Post Reply
jimrac
Posts: 1
Joined: Wed Apr 17, 2019 2:32 am

4.5.2 crashing on iPhone

Post by jimrac » Wed Apr 17, 2019 2:50 am

Hi,

Recently installed 4.5.2 on my iPhone 7 & iPad Air 2, which are both running ios 11.2.5.

My KyPass DB consists of 1 entry that has a spreadsheet attached. (I chose KyPass because it was able to handle attachments.) The DB is hosted on Google Drive.

4.5.2 is working perfectly on the iPad.

But on the iPhone, not so much. I launch the app, enter the master password, which the app accepts. This take me to the root folder. If I tap on the root folder, the app crashes. If I tap on search, I can see the 1 entry, but when I tap on it the app crashes.

My apologies, but I can't remember the last time I used KyPass on the iPhone, so I couldn't tell you if this issue existed prior to the 4.5.2 release.

Any suggestions? Please let me know if there is any info I can provide that would help resolve this.

Best,
Jim

jkhsjdhjs
Posts: 3
Joined: Thu Apr 25, 2019 11:42 am

Re: 4.5.2 crashing on iPhone

Post by jkhsjdhjs » Thu Apr 25, 2019 12:00 pm

jimrac wrote:
Wed Apr 17, 2019 2:50 am
But on the iPhone, not so much. I launch the app, enter the master password, which the app accepts. This take me to the root folder. If I tap on the root folder, the app crashes. If I tap on search, I can see the 1 entry, but when I tap on it the app crashes.
Exactly the same issue here. Bought kyPass a few days ago, haven't been able to use it yet.
I'm using kyPass 4.5.2 on an iPhone SE running iOS 11.3 and I store the database in a WebDAV repo.

jkhsjdhjs
Posts: 3
Joined: Thu Apr 25, 2019 11:42 am

Re: 4.5.2 crashing on iPhone

Post by jkhsjdhjs » Mon Jun 24, 2019 12:16 am

Hey,
It would be great if you could give a short statement on whether you are working on fixing this bug or not.
Thanks!

jkhsjdhjs
Posts: 3
Joined: Thu Apr 25, 2019 11:42 am

Re: 4.5.2 crashing on iPhone

Post by jkhsjdhjs » Thu Aug 22, 2019 1:39 am

I updated to iOS 12 which fixed the issue. Sad that it's listed as compatible with iOS 11 on the app store.

Post Reply