Navigation to new page fails

Question

This is somewhat specific, but I think it is a bug, so the real question is if there is a workaround. Here is the code:

        protected override async void OnNavigatedTo(NavigationEventArgs e)
        {
            base.OnNavigatedTo(e);

                if (condtionMet)
                {
                    try
                    {
                        Frame frm = Window.Current.Content as Frame;
                        if (frm == null)
                            frm = new Windows.UI.Xaml.Controls.Frame();
                        Window.Current.Content = frm;
                        frm.Navigate(typeof(ErrorInfo));
                        Window.Current.Activate();
                        return;
                    }
                    catch
                    { }
                }  
                //some more code here
        }

I use this on Receive page of ShareTarget. The result is that sometimes error page is shown, and sometimes not for the same source target, but exception is never caught as code after return is never executed. Any ideas except to have more controls on the receive page and show/hide them when required, or to check condition onShareTargetActivated and then load proper page from there?

Answer 1

Can you post a simple repro of the issue on OneDrive?

---

Jeff Sanders (MSFT)

@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)

Answer 2

can you please be more specific in what you're asking?  The only thing I can figure out is that there's an error that occurs during the share contract, and it's not being caught.

---

Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.

NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

Answer 3

It is pretty specific

                        frm.Navigate(typeof(ErrorInfo));
                        Window.Current.Activate();

should open the page, and it doesn't happen always if you try several times in a row.

Answer 4

I'll try sometimes later, but I have decided to use workaround for now, so I am now just curious whether this is a Windows bug or not.

Answer 5

No it is not.  Thanks for checking!

---

Jeff Sanders (MSFT)

@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)