An email is invited with lowercased email first and uppercased version of it last in same request
It adds the member for the lowercased input with lower case and then errors about the second one being added since we try to save it with the same casing(lowercased). We can't really get around this one very well unless we do a larger code re-write since the same invite process is used for updating and for that I have to 'find' members by the original case sensitive input and not modify it. However, for new user records, we lowercase that input before it gets to the database. Therefore when a member is added with lowercase first, it is a new member record, and when we try to find an existing member record for the 2nd uppercased one, we do not find it and create a new record, but attempt to insert it into the database in lowercased format. At that point we now have a uniqueness validation issue since the database already has an lowercased version of the member record from the first item that was added.