Apple has rejected our first submission of the iKeePass update version 1.1 due the use of one so called non public function. This function is shown in many sample around the net and in many books. So if you are a iPhone developer, be careful what you use.
We will change these function calls and try again.
Is that the same jbiKeePass that sends your passwords to an unknown third party?
Just kidding – I don’t know this for a fact; however the point is how do you know it doesn’t?
@Dave: and how do you know that the normal iKeepass does not send your password to unknown third party? …you never know that if you don’t compile the application yourself and inspect the sourcecode before…
Hi karsten. Could you give us any idea when this be available in the UK? Thank you.
karsten, did you eventually read about the relaxed and improved procedures for approving apps over at apple?
Any chance you would give it another shot as some folks report about several api calls not being a drawback any more?
Ja ich bin nun auch auf mSecure umgestiegen. Perfekte Software, läuft und ist vor allem auf der ganzen Welt einsetzbar ohne Jailbreak.
Schade das ich von Keepass abschied nehmen musste. Aber über 1 Jahr auf die Iphone lösung zu warten kann es einfach nicht sein…
@Dave: strange humor. You have to trust our word, or go the hard way and build your own iKeePass. The sources are available at github, but you need a Apple Developer Licence and create your own provisions.
hat jemand hier mal MyKeePass probiert/gechecked?
http://itunes.apple.com/de/app/mykeepass/id353354895?mt=8
[...] like Locale could never make it on to the iPhone. Using Apples own internal private API can also land you in trouble, without you even knowing about [...]