-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basic error message tests with bug reproduction #16
Basic error message tests with bug reproduction #16
Conversation
Hi @brodybits, Thanks for looking into this further. I wonder if it would be beneficial to use the |
025639d
to
526ef05
Compare
I just updated this PR to use I hope this is helpful. I don't know if I will work on a fix anytime soon. |
526ef05
to
68f0960
Compare
@developernotes I just rebased and made some minor updates. These tests reproduce sqlcipher/android-database-sqlcipher#295 and sqlcipher/android-database-sqlcipher#296 that I just raised. The reported messages are displayed by the test runner as well. Can you guys merge this one? |
Hi @brodybits We've just released a new version of SQLCipher for Android 3.4.1, and an update to SQLCipher for Android. We will take a look at this and get back to you. Thanks! |
(with some incorrect error messages)
68f0960
to
5cbbbea
Compare
I just updated this according to the actual behavior of 3.5.5:
As an extra note the PRAGMA cipher_version and "Verify Cipher Provider Version" tests still need to be updated. |
Hi @brodybits I have just uploaded the adjusted tests for |
Hi @brodybits Thanks for this, I've just merged it in! |
On Feb 15, 2017 3:56 PM, "Nick Parker" ***@***.***> wrote:
Merged #16.
Thanks for merging:)
|
These tests reproduce
a couplean issuesI discovered from testing my Cordova plugin:In case of nonsense singe-word SQL statements such as "101" or "false" SQLCipher for Android throws StringIndexOutOfBoundsException with a nonsense error message.no longer an issue in 3.5.5 releaseFor the Cordova plugin I will probably just add a quick fix to deal with the nonsense SQL case.(no longer needed)