Null values are getting written when using a custom put resolver to prevent it

I created a put resolver that looks like this:

public class UserPutResolver extends UserStorIOSQLitePutResolver {

  @NonNull
  @Override
  public ContentValues mapToContentValues(@NonNull User user) {
    ContentValues contentValues = super.mapToContentValues(user);
    if(TextUtils.isEmpty(user.getEmail())) {
      contentValues.remove(UsersTable.COLUMN_EMAIL);
    }
    return contentValues;
  }
}

Bascially if the user’s email is null, I don’t want to override it, so I remove the content value. When debugging, I know it hits this line and properly returns the ContentValues object without the email column.

I know I can use the ignorenull property, but i want to know why this is not working.

[nikitin-da]

Closed for now Feel free to reopen if you got this behavior on some sample code that you can publish 😉

[sreejithraman]

hmm… interesting. yea, i’ll try to reproduce it and let you know if I am successful