Handle case of null organizerEmail in changed event
* A recent change assumed that organizerEmail couldn't be null while
an event was being added. However, there is an unusual case in
which it CAN be null, and this CL handles that case
* Regression caused by: SHA 7f448dcd47
Bug: 2719254
Change-Id: Idb8fc79c898bcd2e53fcc8b3e42d0ba67ba762fa
This commit is contained in:
parent
b6a08f68d7
commit
8c742a4c65
@ -552,7 +552,8 @@ public class CalendarSyncAdapter extends AbstractSyncAdapter {
|
||||
addOrganizerToAttendees(ops, eventId, organizerName, organizerEmail);
|
||||
}
|
||||
|
||||
boolean selfOrganizer = (organizerEmail.equals(mEmailAddress));
|
||||
// Note that organizerEmail can be null with a DTSTAMP only change from the server
|
||||
boolean selfOrganizer = (mEmailAddress.equals(organizerEmail));
|
||||
|
||||
// Store email addresses of attendees (in a tokenizable string) in ExtendedProperties
|
||||
// If the user is an attendee, set the attendee status using busyStatus (note that the
|
||||
|
Loading…
Reference in New Issue
Block a user