Re: org-icalendar export problems

[ypuntot <ypuntot@gmail.com>]

The validator says as follows:

Results
File Size: 19544 lines, 434248 bytes
Number of events found: 103
Number of to-do's found: 541
Problem! Found 10 warnings

Warnings
Blank line detected, specification does not address the use of blank lines near line # 9
Blank line detected, specification does not address the use of blank lines near line # 11
Blank line detected, specification does not address the use of blank lines near line # 13
Blank line detected, specification does not address the use of blank lines near line # 15
Blank line detected, specification does not address the use of blank lines near line # 17
Blank line detected, specification does not address the use of blank lines near line # 19
Blank line detected, specification does not address the use of blank lines near line # 21
Blank line detected, specification does not address the use of blank lines near line # 23
Blank line detected, specification does not address the use of blank lines near line # 26
Blank line detected, specification does not address the use of blank lines near line # 28

Problem! Found 1 error

Errors
Lines not delimited by CRLF sequence near line # 1
Reference: RFC 5545 3.1. Content Lines

Jan 30, 2024 04:30:10 Jack Kamm <jackkamm@gmail.com>:

> Ihor Radchenko <yantar92@posteo.net> writes:
> 
>> CCing ox-icalendar maintainer.
>> 
>> ypuntot <ypuntot@gmail.com> writes:
>> 
>>> I am trying to create an android calendar based on the agenda, and the first problem I am finding it's that I can't import it into android (ICSx^5). I am receiving these errors when trying to do it:
>>> 
>>> Couldn't parse iCalendar ...
>> 
>> May you be able to share the problematic icalendar file?
> 
> If you're not comfortable sharing the icalendar file on a public mail
> list, you could also try out the iCalendar validator, which may help to
> identify the issue with the ics file:
> 
> https://icalendar.org/validator.html
> 
> FWIW, I did try out ICSx5 with the exported ics from a simple Org file,
> and it worked. So we'll need more specific information to fix the
> problem.