Fix EAS sending, which was inadvertently broken by a change in EmailProvider
* syncServerId in the Message table can now be NULL; this broke a test used by EasOutboxService and SyncManager to determine whether there were sendable messages in the Outbox * Changed test to allow for NULL in syncServerId Change-Id: Id76c7a45bc306abe7a927ab2395700f54a01a298
This commit is contained in:
parent
8cb81390ce
commit
3e1c871f04
@ -46,7 +46,8 @@ public class EasOutboxService extends EasSyncService {
|
||||
|
||||
public static final int SEND_FAILED = 1;
|
||||
public static final String MAILBOX_KEY_AND_NOT_SEND_FAILED =
|
||||
MessageColumns.MAILBOX_KEY + "=? and " + SyncColumns.SERVER_ID + "!=" + SEND_FAILED;
|
||||
MessageColumns.MAILBOX_KEY + "=? and (" + SyncColumns.SERVER_ID + " is null or " +
|
||||
SyncColumns.SERVER_ID + "!=" + SEND_FAILED + ')';
|
||||
public static final String[] BODY_SOURCE_PROJECTION =
|
||||
new String[] {BodyColumns.SOURCE_MESSAGE_KEY};
|
||||
public static final String WHERE_MESSAGE_KEY = Body.MESSAGE_KEY + "=?";
|
||||
|
Loading…
Reference in New Issue
Block a user