iPassword Crashes on iOS 9.3.3
Just recently upgraded to iOS 9.3.3. Yes, I jailbreak my iPhone 5s because I like to uniquely customize the looks and feel of my device. Plus it is very impressive. People with plain old iPhones are really jealous.
Also upgraded to 1 Password 6.4.4 (I also have 1Password on my MacBook Pro)
The app launches. I click "Use without an Account"
Brings up Sync choices. I choose "Sync with Dropbox"
Loads Dropbox and asks to allow 1Password access. I click "Allow".
Goes back to 1Password, a brief flash of the main 1Password login screen and then I am on the Choose a Vault page.
The default vault is /1Password.agilekeychain. I click on this vault name in the rectangular box and then it tries to go somewhere (a blank white page) and then promptly CRASHES out to the Springboard page. EVERY TIME.
It asked if I want to send crash reports. I chose "Every Time" and it stopped asking. So I am assuming you are getting the crash reports. Lots of them because I can make it crash every time following the steps above.
I have tried deleting the app and re-installing it. No help.
What's causing this and how can I fix it? All my other apps are working nominally. Except 1Password.
Please help.
1Password Version: 6.4.4
Extension Version: Not Provided
OS Version: iOS 9.3.3
Sync Type: Dropbox
Referrer: kb:undefined, kb-search:jailbreak, kb:undefined, kb-search:crashing when accessing a vault
Comments
-
Hi @FogCityNative,
I’m sorry to hear that you’re having trouble with 1Password. Unfortunately, with a jailbroken iOS, there are some things that we might not be able to fix, but let’s take a closer look at your system to see if we can determine where things are getting tangled up.
I'd like to ask you to create a Diagnostics Report from your iOS device. Please note, this is different than the crash reports you have been submitting. Crash reports are sent anonymously to the developers, this Diagnostics Report will go directly to our support team so we can take a look at things more carefully.
Sending Diagnostics Reports (iOS)
Attach the Diagnostics Report(s) to an email message addressed to support+forum@agilebits.com.
Please do not post your Diagnostics Report(s) in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report(s) in our inbox.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here so we can track down the report(s) and ensure that this issue is dealt with quickly. :)
Once we see the report we should be able to better assist you. Thanks very much!
0 -
Hi, Megan....
Alas, I wish I could send you a Diagnostics Report. But the program crashes too early in the process to even get to any menu that might allow this.
The problem seems to be in connecting to a vault. I have my existing vault on DropBox. I get further when trying to connect to the existing Dropbox vault, but wanted to test to see if the error occurred when reading the existing vault. So I chose "Create New Vault" which caused an instantaneous crash of the application. So it isn't my vault, but your code in combination with jailbreak or custom keyboards.
Since the new Pangu jailbreak is a semi-tethered jailbreak, I rebooted the iPhone which kills the jailbreak. So the phone boots up in an un-jailbroken state. I wanted to see if I could get iPassword to work with the phone in this state.
It worked. I got past the bug, which was tied to entering my passcode for the existing vault and perhaps my use of a third party keyboard for Emoji's as well as some tweaks to give me a 4 line keyboard like an Android so I have both letters and numbers on the same keyboard (Apple needs to steal this tweak as they have stolen so many others in the past, all the while claiming their opposition to jailbreaking and making it harder and harder to hack . . . without the hackers, the unsupervised kids working at Apple without guidance from Steve Jobs would lose the source of their best ideas!).
I turned on the 1Password preference to allow 3rd party keyboards. I realize the writers of these keyboards have access to anything I type on them. Instead of spending development cycles fighting the jailbreakers, Apple should close this security breach. And fix SIRI so it understands words like UBER and stops interpreting the UBER ridesharing service as GOOBER.
Apple bought SIRI because they don't have the talent in house to build such functionality. All the SIRI developers took their money and quit Apple. It would seem Apple has no clue how to get SIRI even close to Google's Voice Recognition on Android. Apparently, Apple is falling further and further behind, which is reflected in their unit sales.
Tim Cook apparently is a super nice guy but he is an operations guy, who is great at optimizing procurement and manufacturing but a failure as a replacement for the genius that was Steve Jobs. Of course, no one ever accused Steve of being a nice guy.
Steve was notorious for never using focus groups or market research on users. A famous quote: "They don't know what they want until I show it to them."
Oh, the good news. I was able to link the vault by entering my master password and allow third-party keyboards in 1Password, then I recreated the jailbreak (takes about 20 seconds to respring) and the 1Password crashes stopped. It WORKS again.
So, the official workaround is to link the vault and allow third-party keyboards in an un-jailbroken state. Wire the 1Password brain first, then turn on the jailbreak and 1Password will be fully functional.
Case closed (unless you guys want to add some code to make sure the keyboard used to enter the vault password is a default keyboard.)
0 -
Thanks for the update, @FogCityNative.
unless you guys want to add some code to make sure the keyboard used to enter the vault password is a default keyboard
iOS itself has a mechanism built-in to prevent non-standard keyboards from being used in password fields, but it sounds as though the jailbreak may remove this protection?
Historically our developers have not been receptive to fixing issues caused by jailbreaking, but I'll be happy to pass the feedback along.
Ben
0 -
Thanks, Ben...
Not a big deal because the workaround solves the issue. The actual app works great on a jailbroken device. It is just the initial setup that fails.
0 -
Good to know that worked for you! Cheers! :)
0
