Unfortunately, Google is known for exporting broken opml files. We had all kinds of format violations with their files already.
The error message prints the line that is not valid opml. It misses a slash before the closing >, like this: text="..." />. Some other apps have more workarounds to guess what broken opml files are actually supposed to say, which is why they do not complain. Unfortunately, accepting broken files creates a world of more and more broken files with more and more workarounds required.
You can open the file in a text editor and repair it manually by adding the slash. Probably needed in several lines.
Agreed, and reporting the broken OPML files to Google probably isn’t an option anymore since they are retiring Google Podcasts.
That said, I understand that people who had trouble and made another export later seem to have generally had success. I was fortunate to have success on my first attempt when I migrated from Google Podcasts to AntennaPod earlier this year.
