I have a banner with a link defined as "navto://collection/september_october_2016/article/so16_oow_preview". The banner is used on the "september_october_2016" collection browse page. In this context, the link sends the user to the first article in the collection, not the article named in the link.
If I put this same link on a banner in a different collection's browse page, it works fine. In other words, it appears that the "navto://collection/[collection_name]/article/[article_name]" format doesn't work if you are trying to point to create a link on a banner that points to the same collection that contains the banner.
This problem only occurs in iOS preflight apps, not Android preflight apps. I tested with version 2016.11 in both cases.
A "navto://article/so16_oow_preview" link works fine, but then I don't get the ability to swipe left or right to adjacent articles in the collection.
Jay, your note prompted me to test this in another, simpler test app that I have. And of course, it worked fine in that app! But, the levels of nesting of the collections and articles are exactly the same as the problem app. The only difference that I can determine between the 2 is that the app in which I'm having problems the collection is not yet published, where in my test app it is published and out of date. But in both cases I'm preflighting. The other difference is that my navto link is quite lengthy because the collection name is quite long. Is there perhaps some sort of restrictive character limit?