Thanks for the clarification Bob. I've tried this and it works great.
One point to note, it's case-sensitive.Since you can reference the same
article in multiple places, like with a "Top 5" list and also a
"feature" article, I wonder how the app would know which one to navigate
to? (not particularly important, just speculating)We definitely look
forward to using navigation to collections. We also have some ideas for
navigating out to the browser, please keep this under consideration.
Will we be able to navigate to other collections or articles
example, is there a deep-link name attached to content, or are custom
The app started working all of a sudden, anything happen on the Adobe
side you're aware of?The only new thing I tree was to hit the "Preview
All Content..." button to the right of the project drop-down, thinking
this might be another data point to check on status of content. (It
didn't seem to do anything)Could that have corrected whatever was going
wrong with content on the backend?
I just tried this again using a developer's sub-account, thinking maybe
another fresh start would help. Still no luck.I'm deploying to an iPad
2, single default collection.Btw, Folio Migration works from the
sub-account, but publishing that collection and adding it to the default
didn't solve this Content Not Found issue.