We have tried to adhere to the standard use of symbols. If they are not organized correctly, the results in the player are unpredictable. While we could code in error messages and attempt to figure out what someone wants (by where they have placed the symbols) for playback, it would complicate the code (and take up hours of our time.) For normal use, it should respond as needed, if unsure, then post it with your intended form for someone to look at - and often there are different ways to lay it out, some being more successful for playback than others.

Slightly related: a complex song can be difficult to figure out how to lay out, easier perhaps if a chart is only used visually as you can add text ('2nd and 4th time no repeats' for instance and a person will know what you want) but the player is programmed in a basic way. Sometimes it is best to copy/paste below to repeat some of the sections so it plays back correctly, sometimes however it is a compromise between visual and player behavior; other times a human can get confused as to what is intended anyway.

We make slight adjustments to how the player interprets form from time to time in order to accommodate particular instances, but in this specific case the orphaned closing repeat in the final measure does not make sense (chorus count is controlled in the player window if the song was to be played twice through.) You can have a closing repeat at the end without the matching open at the first measure, but not if there is already an open repeat there being paired with its closing repeat; otherwise repeats are normally in pairs. (iReal b has not been programmed to understand nested repeats either - Android v2.1, iOS v4.6, Mac v2.8.)

I hope this all makes sense to anyone else following our discussion here
Thanks Larry, Bob, DaleMac
- further discussion welcome.