I have a UWP app, published in store, here. The app hosts AdControl in some pages and the current version of the app has AdControl but I have no way of confirming if the app is working on other systems but it's not working on my laptop (Windows 10 Creators Update - clean install).
This issue has just recently popped up when my Store submission failed twice and the reason was that my app wasn't launching at all. The app was working fine in Debug mode but when I compiled the app in Release mode, it was actually not working. I have no other windows systems to check if it is a system specific issue just related to my laptop or maybe it is related to AdControls everywhere.
If the pages in my app doesn't have a AdControl the app works fine. I debugged the code and it would not pass through the Page Initializing function, and there I found out that while initializing the pages, the last thing to pass through was the AdControl and when I removed the AdControl the app was working fine and it would still navigate to those pages without AdControl.
Did someone else experience this issue? Maybe download my app and let me know if it works on your system.
this is how I am using the AdControl:
xmlns:ads="using:Microsoft.Advertising.WinRT.UI"
<ads:AdControl Grid.Row="4"
x:Name="Movies_AdControl"
Margin="0,10,0,0"
AutoRefreshIntervalInSeconds="15">
</ads:AdControl>
and also in the VisualStateGroup
<Setter Target="Movies_AdControl.Height"
Value="50"/>
<Setter Target="Movies_AdControl.Width"
Value="320"/>
#Ahmar, there is a known issue with the Windows 10 UWP AdControl that started about a week ago. Unfortunately the AdControl is part of the framework ad sdk which means Microsoft can push out updates to it any time and break all the apps that use it (which is exactly what they did last week).
The reason your new project might work is because you are doing very little other work in the Page contructor. It seems to be a timing glitch that prevents the Loaded event from ever firing (not all of the controls on the page initialize). Try putting a bunch of other controls on the page and you might be right back to having the problem.
The good news is that the problem was finally fixed with the Ad SDK 10.0.5 which has internal version numbers of 10.1705.11001. The bad news is that even if you build your app with that version of the sdk and submit it to the Windows Store, it is still possible that your users have the older broken sdk and until that update is pushed to everybody, there will be problems.
The idea of store framework packages is a bad idea to me. Good in theory due to smaller downloads and potentially rapid and automatic deployments by Microsoft, but bad when Microsoft is sloppy like they were here.
Discussion:
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/1d5e1f23-bd61-4384-b55c-2d0cae8d4a03/new-adcontrol-freezes-apps?forum=aiasdk
Related
We are developing an UWP App that needs the ability to drag items from one GridView to another.
While testing this functionality we encountered multiple catastrophic failures 0x80000FFFF.
After almost 2 days of research we were not able to find a solution for our problem.
We found out that these failures happen, when there's an ItemTemplate set for the GridView the item is dragged from.
Even trying out the official drag-drop sample provided by Microsoft “XamlDragAndDrop”,(https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/XamlDragAndDrop), when you drag the items in Scenario1 from the source ListView to the target ListView (~30-50) times, you will encounter the failure as well.
Has someone else encountered this problem before? We would be super grateful for any advice!
Our developing machines run Windows 10 Enterprise, Version 1803, OS build 17134.285.
Opened an issue on the official GitHub repo.
https://github.com/Microsoft/Windows-universal-samples/issues/977
I recorded a small video of the sample crashing.
https://1drv.ms/v/s!AiZ-jksNqbXLi9kZPPfSeGmQr_YeHg
We managed the get the native trace here.
When running in release mode its crashing earlier, and also when the redraw function is turned on in the display heatmap section.
According to the Raymond Chen this is a plataform specific problem which was solved in the Windows 10 May 2019 update.
So the solution is: update your version of the windows to the latest.
Find out here how you can update it.
Windows 10 May 2019 (What's new)
Windows 10 May 2019 changelog
Im having problems getting the Reminder notification to launch my App once it's touched. Through the MSDN step by step guide and documentation found HERE, I know that, if the user does not touch any of the buttons (snooze/decline) but touches the popup itself, the Uri defined in the reminder should be opened inside the App. However, once I do that, not even the App itself is launched, let alone the specified Uri.
To make sure the problem wasn't on my App, I've created a new application and copied the exact code found on the page linked above, and while it does schedule a Reminder, once it pops up, touching it only makes it disappear, still not launching the App nor the specified Uri (which exists, yes).
I've already searched a bit around here, and even though I've found a couple of questions similar to what I'm asking (such as this one), it relates to WP 7, while Im having problems with WP 8.1.
The user in the previously mentioned question figured out by himself that one needs to have the app closed for the popup to launch it at the specified Uri. However, even doing so, nothing happens with me, both on the emulator and the device. I have even removed it from the suspended/previously used apps, but still nothing happens.
I have also found this, but nobody answered, and I don't have enough rep to comment on his question asking if he found the solution :/
I'm using VS 2013 Professional Update 3, Windows 8.1 Pro 64 bits, The Windows Phone 8.1 SDK and Emulator and a Nokia Lumia 620 with Windows Phone 8.1 on it. My apps are Windows Phone Silverlight 8.1. If anyone wants, I can link to the binaries for the test app I've built, but it's really a copy & paste from the tutorial from the first link I mentioned.
If anyone could help me on this, I'd reeeeally appreciate, because I feel like I'm missing something really small and stupid, but can't figure out what. Other than that, it just seems like a bug on WP 8.1.
Thanks in advance, and sorry if it's an already solved question, but as you can see, I tried to find the answers and couldnt...
Just wanted to say, to whoever finds him/herself struggling with this problem, that I - sort of - solved this problem.
I got in touch with a Microsoft Developer Evangelist who told me that indeed, this feature was removed from the 8.1 API. He refused to admit it was simply a bug, even though he agrees on that fact that the "Uri" property still being there is confusing. I'm not sure whether to believe him or not on this matter (I still think it's a bug), but at least I found out the problem was not me.
In the end, the only viable solution was to convert the whole project back to WP 8.0. Since Visual Studio does not allow one to do it by simply editting the project file, I had to copy all files to a new project by hand. Luckily, there were no major issues while doing so. Now the "go to URI" behaviour works just fine!
Hope it helps someone :)
While running performance tests my application suddenly started giving blue screen shortly after the UI was loaded.
In the code im receiving the following error:
{"Error HRESULT E_FAIL has been returned from a call to a COM component."}
"The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.\r\n"
After looking around on google i wasn't able to find anything usefull. The main answers given didn't work such as installing driver updates or reinstalling the application. Keep in mind this is an app in development and it was working fine earlier this day. Between two test launches this happened.
EDIT
After testing the application on a tablet it turns out the development pc is the only machine with the UI loading bug. Going to look into it some more and ill let you guys know if i find a solution.
Edit 2
So after testing the app on the tablet and finding that it works fine there we decided to test the app on a 2nd development pc. Needless to say the same thing happened... in other words its a rendering issue that happens on windows 8.1 PC's but not on a tablet.
Facts as of now:
- Code worked yesterday, no longer works now
- Works on tablet but not on PC
- Nothing changed in the code since it worked
- Seems to happen in the rendering stages
- Bug happens when loading more than 23 items in a listview, app restores itself then
- Any more than 23 items and it stays bugged (dark blue screen but still responds to clicks)
Reading the following (and skimming other areas of the site):
http://msdn.microsoft.com/library/windows/apps/br211361.aspx
It seems as though I have to re-write a program I've been writing in VC# 2010, to be able to put it on Windows Store. Is this true? Can I simply import my project into VC# 2013 and then put it out there? Is there a reason I shouldn't do that even if I could (i.e. it looks different than other Windows 8 apps and users will be off-put by it)?
If I can't import and release my project into Windows Store directly, and this is a little bit of a tangent, but, can I at least import it into Visual Studio 2013, and then begin rewriting/adding the parts I need to to be able to make it compatible with Windows Store? I've never used app stores before, so please be gentle.
In most cases, opening a VS2010 project in VS2013 is not a pain.
You can find 2 kind of apps in the Windows Store :
Modern UI apps (aka Metro)
Desktops Apps
If you want to create a Modern UI app you need to target the .Net 4.5 framework. To do so you need to upgrade to VS2013.
But most of your work will be to rewrite a huge part of your program as the modern UI is not compabible with WPF (and you will need to manage touch devices). Other assemblies also doesn't have all the features of the desktop ones, so you will probably have a little bit of work in that area too.
Here is a link that explain the process of publishing an app in the Windows Store : http://msdn.microsoft.com/en-us/library/windows/apps/jj657972.aspx
If you want to publish a desktop application it seems to me that you only need to provide an URL to download your package. Be careful it is not possible to submit that kind of app with a personal account, you need a company account to do so. You can find more information about that process on MSDN: http://msdn.microsoft.com/en-US/windows/desktop/dd535817
I'm developing an application that will be executed in a ThinClient with Windows Embedded 2009. It's written in C# 3.5. But, when I played for the first time with the ThinClient, I noticed that it has a lot of features disabled.
For example, there is no MyPc, or I can't have access to it.
So, my app needs to run when the client is turned on, but I can't find a service manager in embedded 2009.
Is there a way to make my app run every time the client is turned on?, I thought about a service, with automatic start. Can this be done like a windows service with no problems?
And another thing. My app also has to shut down the client. I've found a way to make it, but, I'd like to know if is different in Wndows Embedded.
Btw, the device has no hard disk.
Any other suggestion, will be very appreciated.
Have a nice day.
In the older Embedded there is a "startup"-folder (located on the flash-card containing the win-image)