-
Notifications
You must be signed in to change notification settings - Fork 427
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
Must specify an iv when adding form field #306
Comments
I'm getting the same error randomly when processing encrypted values within the code (read only). |
@dessery85 what does your schema for that object look like? |
Downgraded the gem to version 3.0.3, no |
Yet another update from my side: I was able to reproduce the situation in the development environment by triggering multiple, heavy read-write operations on the AR objects using encrypted attributes. I also investigated production logs and there is a strong correlation between the occurrence of the |
Any updates? Having the same issues. |
Any updates? |
@szymonbaranowski This PR looks like it could be addressing the same issue you're talking about: #320 |
Same Error for my form
|
Hi
I have just started to use this gem to encrypt email addresses in our database. I have created a script to programatically convert values from an existing email column to a new encrypted email_address column and this works fine, both encrypting and decrypting. I am now trying to update my views to output form inputs for the new column but when i do I get the follow error:
Must specify an iv
The code I am using is:
<div class="input-field"> <%= f.label :email_address, 'Contact Email:' %> <%= f.input :email_address, label: false, :wrapper => false %> </div>
Should this work? Or do I have to just add a field with a different field name using attr_accessor on my model, then programatically save that value to my email_address property on save? I couldn't see any examples on how best to approach this.
Any guidance would be greatly appreciated!!
Many thanks
The text was updated successfully, but these errors were encountered: