7

In Visual Studio 2015 Update 3, I have created a JavaScript -> Windows -> Windows 8 -> Windows Phone -> Blank App (Windows Phone) project. I then changed the default.html to include a <select> element like this:

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <title>App1</title>

    <!-- WinJS references -->
    <!-- At runtime, ui-themed.css resolves to ui-themed.theme-light.css or ui-themed.theme-dark.css 
    based on the user’s theme setting. This is part of the MRT resource loading functionality. -->
    <link href="/css/ui-themed.css" rel="stylesheet" />
    <script src="//Microsoft.Phone.WinJS.2.1/js/base.js"></script>
    <script src="//Microsoft.Phone.WinJS.2.1/js/ui.js"></script>

    <!-- App1 references -->
    <link href="/css/default.css" rel="stylesheet" />
    <script src="/js/default.js"></script>
</head>
<body class="phone">
    <select>
        <option>Val</option>
        <option>Val</option>
        <option>Val</option>
        <option>Val</option>
    </select>
</body>
</html>

When tapping on the select element, the application crashes on Windows Mobile 10 with:

'WWAHost.exe' (Script): Loaded 'Script Code (MSAppHost/2.0)'. 
The program '[3976] WWAHost.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'.

This happens on devices and the Windows Mobile 10 emulator. Windows Phone 8 does not seem to have this problem. Until recently, this worked fine on Windows Mobile 10 as well. Perhaps an update caused this? Interestingly, Cordova and UWP are also affected. Is there a known solution yet?

Deathspike
  • 8,582
  • 6
  • 44
  • 82

1 Answers1

2

I am experiencing the same issue. I don't have a fix but I can at least explain what I have found.

  • I tried using WinJS 2.1 and WinJS 4.4
  • The select element works just fine on Windows Phone 8.1 and Windows 10 (Desktop)
  • Edit #1: I have now tried doing a full reset on my phone and installing everything from scratch again - it would appear that it pulls in the latest update when you do a reset - so this didn't help at all.
  • Edit #3: I tried setting all different kinds of listeners (onclick, onchange, onmouseover, etc) and none of them ever fire. The crash happens before these events.
  • Edit #3: I tried completely restyling the select element with CSS. No luck.

It seems like we both discovered this issue right around the same time. This would lead me to believe that this has been caused by a recent update. Hopefully there will be another update soon to fix the problem.

I sent an email to MS support asking for more information, I will let you know if I find more. I was trying to think of alternates to use instead of a select element - but I really couldn't come up with an easy solution. I am at least going to wait a while before I have to rewrite all of my select elements.

I know this doesn't help much but I will be sure to update my answer if I find anything!

EDIT #2: Here is the crash dump straight from the phone.

EDIT #4: MS support basically blew me off and told me to go post the problem in their technical forums. Feel free to check out my post (hopefully get it more traction) or post your own thread.

EDIT #5: I have officially given up on looking for a work around. It is broken and I (nor anyone I have seen) has been able to get around the issue. I had to replace all the elements to drill off into a new screen with a ListView. It's upsetting that we have to reinvent the wheel to achieve something so simple.

Stephen Ruda
  • 585
  • 2
  • 11
  • I'm very glad I'm not the only one with this issue! Thank you for your answer! I guess we'll both be waiting for that support e-mail :-) – Deathspike Aug 25 '16 at 07:26
  • This seems key. `10.0.14393`, the anniversary update, is the culprit. I just found out that background tasks (specifically, geofence) don't seem to fire anymore, either, so more than just this is completely broken. – Deathspike Aug 26 '16 at 13:39
  • Related problem I presume: https://stackoverflow.com/questions/39167898/windows-10-mobile-10-0-14393-background-task-for-geofence-locationtrigger – Deathspike Aug 26 '16 at 13:47
  • @RoelvanUden Interestingly, I also use a background task and Geofences in my app - but they are still working for me. It could be in a difference in the way that we set up our background tasks. Mine is all done in javascript and I have no c# code at all. If you would like me to post some of my code on your other question, I can certainly do that. Also, as far as my emails to Microsoft, they have not been able to reproduce the issue yet :( – Stephen Ruda Aug 26 '16 at 16:47
  • Updated my response with Edit #4 regarding Microsoft's response – Stephen Ruda Aug 26 '16 at 20:48
  • Yeah, I gave up too. Thanks for sharing. I also made a custom component for something so basic. – Deathspike Sep 01 '16 at 15:04
  • 2
    I reported this issue to Microsoft and it was marked as fixed a few hours ago. It seems to affect Windows Phone 8.1 apps rolled out on Windows 10 Mobile (10.0.14393) only. So I guess, as soon as this fix is rolled out, everything should work as expected again. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/9529349/ – christianliebel Nov 18 '16 at 06:45