User Registration Add-On: the user's mail has already been used on update

Software I'm using:
- Gravity Forms: 1.6.11
- Gravity Forms User Registration Add-On: 1.5.beta1
- Wordpress (single site): 3.5

I'va created 2 gravity forms with the same fields and setup one of them for user registrations and the other for user updates. The registration form runs as expected. The update form, when saving, tells the user that its email has already been used (the field requires a unique entry; the same occurs with other fields set to be unique). I thought that the plugin should check if the user's data is the same and, in such case, don't update it on saving the information. Maybe I'm doing something wrong? Is this a bug?

Yes, that is. Not only the email address, also another field that should be unique as well (ID card).

I can send you private access to the website by mail if you need to test it. If so, tell me what do you need.

Just curious if there's a solution to this - I have the same issue. My "email" field is set to "No duplicates" - and if I uncheck that box, then it works fine. But if it's checked, and the email address is unchanged, it won't submit the other changes in the profile. It just returns with an error.

OMG, I swear I did NOT post this! LOL I wrote it, then I thought I'd troubleshoot a bit more. I bet one of my kids came by and clicked something. So sorry. Okay, well since I'm here! XD

I have my user registration mapped to an "edit profile" form. The email address is set as "required" and "no duplicates". When the profile is updated (from the front end), the form is supposed to go to the profile view page (custom redirect I set), but instead it returns to the form with the standard "this email is already in the system" error. (If I change the email address, it works just fine.) It seems that GF isn't noticing that this is an *update of the profile, not a new registration, and it's tossing out "this email already exists" and won't update.

If I uncheck "no duplicates" in the form, it's fine. Which seems to work out okay - this is only for an update, and will only update the logged-in stuff. It's not it'll register a new user (or mess with a forgotten login to the same site - which I'm prone to do, myself) if I update and use an email that already exists with in the system.

There's no actual *error* messages (as far as the PHP error logs go) - it's just your standard "this email is already in use" message on the front end. My workaround is fine for our purposes (I can't see any reason why it would make things wonky), but if you want a login to the site I'm working on to see how it's setup, I can pass it to you.