locked
Windows Phone 8.1 Update 1: App crash on frame.navigate in selectionchanged on listview RRS feed

  • Question

  • Hi,

    I've developped an app for Windows phone 8.1 with WinRt.

    It has been working quite well but today with the release of update 1, the app crash when I select an item (a problem with frame.navigate in a listview).

    If I call a blank page, in a selectionchanged method from a listview the app crash with an access violation error but when I call this blank page on a button, there is no error.

    Could you help me? I've tried to search in my code where would be the error but as it was working before the update, I suspect something change on a listview?

    Regards,

    Ugo

    Monday, August 4, 2014 11:05 PM

All replies

  • Sure Ugo!

    What troubleshooting have you done so far?  Have you been able to isolate the issue to a section of code?


    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)

    Tuesday, August 5, 2014 12:15 PM
  • Hi Jeff,

    Thanks for your answer.

    It seems the problem is related to the slideview lib that I'm using.

    After disabling it, the listview works again.

    I will try to contact the developper to know if he's awared of this issue.

    Thanks again.

    Ugo

    Tuesday, August 5, 2014 1:11 PM
  • OK great!  Thanks for sharing Ugo.  After the library author fixes this issue could you post the name of the library and how to get the fix so this will help others?


    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)

    Tuesday, August 5, 2014 1:33 PM
  • Yes sure, if the library is fixed.


    Wednesday, August 6, 2014 2:17 PM
  • Hello,

    I have been having the same issue.

    My exception happens when I click on an item inside a ListView. I hooked up the ItemClick to a command using:

    <i:Interaction.Behaviors>
        <core:EventTriggerBehavior EventName="ItemClick">
            <core:InvokeCommandAction Command="{Binding SelectGameCommand, Mode=OneWay}" />
        </core:EventTriggerBehavior>
    </i:Interaction.Behaviors>

    I have tried to debug the SlideView without any success to capture any form of exception. The only thing that has worked so far is to remove the SlideView from the page.

    I will post any update if I can find something.

    Saturday, August 9, 2014 7:25 PM
  • Hi,

    I am the author for the SlideView library :)

    Can anyone send me a minimalist sample to reproduce and fix the bug please ?

    Thanks for reporting it anyway, I'll try my best to fix it.

    Sunday, August 10, 2014 9:45 AM
  • This post is purely for reference for future reference.

    I did raise a bug on the issue tracker of the project not long after I initially posted here. More information can be found there:

    https://slideview.codeplex.com/workitem/35453

    Sunday, August 10, 2014 4:05 PM
  • Hello,

    It seems that this is not related to the SlideView but rather the navigation that is not happening on the UI thread. You need to call the dispatcher to perform navigation.

    Refer to this thread for more information:

    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/6d1a6be3-096e-4090-a4bd-30d1293697b3/windows-phone-81-update-1-access-violation-when-navigating-using-tapped-event?forum=WindowsPhonePreviewSDK

    • Proposed as answer by Marais van Zyl Wednesday, August 13, 2014 5:47 PM
    Wednesday, August 13, 2014 5:46 PM
  • Hi,

    Do you still have that issue? There is update for Developer Preview Program but even after that update I still get Unhandled exception at 0x6B7585DE (WINDOWS.UI.XAML.DLL) in WindowsPhone.exe: 0xC0000005: Access violation reading location 0x00000034.

    Regards,

    Aleksandar

    Thursday, October 2, 2014 8:17 AM
  • Hello,

    Did you try navigating using the despatcher as suggested earlier?

    Regards,

    MS

    Thursday, October 2, 2014 8:20 AM
  • Hi,

    Yes I've tried this and it's still the same, no luck with that.

    Regards

    Thursday, October 2, 2014 8:31 AM
  • Hi,

    Ok got it. Actually navigating using dispatcher seems to solve the issue, but when I've first tried that I used my extension method in which I check if dispatcher has access to the tread or not and the weird thing is that dispatcher.HasThreadAccess is true but after that it throws "Access violation exception". But if I call dispatcher.RunAsync without checking dispatcher.HasThreadAccess property it works fine, anyway I suppose there is a bug in that Update.

    public

    staticasyncTaskInvokeIfRequired(thisCoreDispatcherdispatcher, DispatchedHandleraction)

            {

               

    if(!dispatcher.HasThreadAccess)

                {

                   

    awaitdispatcher.RunAsync(CoreDispatcherPriority.Normal, action);

                }

               

    else


                {

                    action();

                }

            }

    Regards

    Aleksandar

    Thursday, October 2, 2014 9:55 AM
  • Hi,

    I've uploaded sample code to one drive where that bug can be reproduced: http://1drv.ms/1uDz3n3

    Regards,

    Aleksandar

    Thursday, October 2, 2014 10:55 AM