ENDVEVENT

ENDVEVENT is not a standard marker in the iCalendar specification. In the iCalendar format (RFC 5545), calendar data are organized into components such as VEVENT, VTODO, and VJOURNAL, each delimited by BEGIN and END lines. For VEVENT, the correct end tag is END:VEVENT, not ENDVEVENT. There is no ENDVEVENT in the official specification.

Origin and usage

ENDVEVENT may appear in files produced by non-compliant editors, templating systems, or by typographical error. It can also result from automated generation that concatenates words without the required colon. Because the RFC schema relies on exact component boundaries, ENDVEVENT does not match the expected END:VEVENT end marker used by compliant parsers.

Impact

Files containing ENDVEVENT are likely to fail validation or be rejected by calendar applications that enforce RFC 5545 conformance. Some parsers may ignore the line or treat it as an unrecognized token, but this generally leads to incomplete parsing of the VEVENT or propagation of parsing errors to subsequent data.

Corrective action

If ENDVEVENT appears in an ICS file, replace it with the correct end marker END:VEVENT. After making the correction, validate the file with a standards-compliant ICS validator or a calendar library to ensure proper parsing. Adhere to the standard BEGIN:VEVENT / END:VEVENT structure for VEVENT components and ensure consistent line folding and encoding per RFC 5545.

See also

iCalendar, VEVENT, BEGIN:VEVENT, END:VEVENT, RFC 5545.