Just in several hours after LateReader v.1.2 being published, I received an error report saying that “No XAML found at the location XXX”. Wait, but that’s an old URI, used in the previous versions, where did it come from? Turned out that a secondary live tile which quickly adds a new article to the list still uses the deep link URI, created with the previous app version. The morale is: keep the backward compatibility in mind and use UriMapper to deal with such tile navigation issues.

And v.1.3 that fixes this bug and some other minor issues is already submitted for the certification :)

Leave a Reply

Your email address will not be published. Required fields are marked *