I've got a small problem that im not quite sure how to solve, i perform regular updates to my windows phone apps in C#, the problem im having is sometimes when some people update the app it wont open for them and this is only a very few people. Even after removing and reinstalling the app it still won't open, i can't recreate this error myself ive tried, but the weird thing is the last time i updated and got a complaint i only changed one thing a url in a webbrowser which has no actual effect to the app and it caused this problem, any advice on what could cause it, maybe isolated storage if so how or advice on how to get an error for the app.
Related
I am developing an ASP.NET MVC 5 application for a while now.
After an update that changed a lot the database structure, the UI has gone crazy. I think this is a IIS issue since it is only on the client's machine and I am not able to replicate it, but I don't know where to start looking for it.
I have tried to restart everything, but with no resolve.
This is going on for days and I am out of ideas.
As it can be seen in the picture, the CSS is not working correctly, the pictures are not showing and the Resource data (for switching the language) is crazy.
I don't know if the update did something or not, but it shouldn't since I changed the models and controllers only. I did delete some screens, but this shouldn't impact.
If I deploy it on a fresh machine there is no problem.
I know this question is really ambiguous, but I have looked into the cshtml files are I could't find errors and I do not know what info / code to give. I can update if someone can help.
Update:
Thank you for all your responses. Sorry for my late one. I didn't expect answers so fast. Here is how it looks on mine:
The bigger problem is that I do not have access to their server. I am working with somebody else on the phone and they send me pictures.
UPDATE 2:
It didn't work with CTRL+F5 and clearing browsing history (I didn't thought about this since it is the same on two laptops they are using to access the app). They are not allowed to install other browsers than Mozilla and Internet Explorer. They are using Mozilla by default. Opening the app in Internet Explorer improved the situation. The Resource works and the CSS is improved, but the pictures still aren't showing.
This is how it looks on IE:
They use a laptop as a server and access the app on 2 other. It is a temporary solution until a server will be bought.
I am having severe problems getting an app working in Retail Mode on the Xbox One.
The app works fine in Dev Mode, I have uploaded to the store and it passes certification fine but when the app is then installed via the store onto a Retail Xbox One it refuses to run.
Firstly it was crashing whilst on the splash screen, no error message just returning back to the Xbox homes screen, Due to now being in Retail mode I cannot connect a debugger to the app. I've setup my own exception handler to send errors to my backend server and it was crashing with the exception:
Cannot create instance of type 'Microsoft.Advertising.WinRT.UI.AdControl'
It's using the latest Microsoft.Services.Store.SDK and therefore Microsoft.Advertising SDK for XAML. I've took out the AdControl from MainPage.xaml and now we have a UI come up on screen! Not ideal as the ads are needed for monetization.
Unfortunately that's not the end of the problems, during the app initialisation it copies files from the Data folder of the solution to localstorage, for some reason it's now hanging on the following:
StorageFile anjFile = await localCacheFolder.GetFileAsync(App.AbilitiesFileName);
What's so different running apps on the Xbox in Retail Mode compared to Dev Mode? The app also functions fine on mobile and desktop so I know there shouldn't be any problems. The only way to try and find out what's causing problems is to comment out lines, or put placeholders in the app to change a debug textbox on screen to see what part of code is running and rebuild and submit to the store again, wait for certification and then redownload from the store to the Xbox, a very slow and time consuming task and I'm now up to Submission 12 of an app I'm getting very frustrated with!
Update: Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.
Thanks a lot for reporting this issue out on the forum and helping us with investigations. The root cause of the issue has been identified and fix has been rolled out. The framework update will take a couple of days to reach most devices as and when any new app or updated ad-enabled app gets updated on the Xbox device.
Dev Mode only: The issue doesn't affect Dev mode and only Retail mode since Retail mode actually is the most secure and most strict environment and requires that all binaries involved are signed and certified. If anything is missing, Retail mode is the only one which will surface the issue in this fashion - not loading the libraries.
Fix and roll out process: You could reach out to the users who reported problems for your app and ask them to re-install your app. The other option that you (as a developer) have is to push an update to your app (only version change) and push it to your users. This will get the framework updated on the end user devices and speed up the fix roll out. Those developers who had taken off the ad control, please put it back and push the update for your apps.
Please feel free to reach out to us (msft-aia-help#microsoft.com) in case of any issues or queries regarding this topic. Thanks for the patience and sorry for the inconvenience caused during this period.
-Vivek.
Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.
I have got a update from our engineering team, this issue has been fixed. But you may need to uninstall and reinstall any of the affected apps in your XBOX, after that it should work fine.
Please let me the result after you reinstall all the affected apps in your XBOX.
Thank you.
I am (was) experiencing problems with my WPF application completely locking up my computer (it would freeze mouse/keyboard so no CTRL-ALT-DEL, although the hard drive could be seen to be working still) which is the exact same issue discussed in this question, however the solution there is not relevant.
I then found this question which (seems) to have proved the mustard (basically, the issue was that Comodo firewall prevents applications from accessing DLLs willy-nilly without user confirmation and since the WPF app was prevented from accessing DirectX.dll it somehow causes a system freeze before Comodo can even display the confirmation dialog).
I started writing this before I found the second question and my question was basically going to be "WTF?".
Now my question is there some way around this? Does anybody else see this sort of behaviour? I just find it hard to believe that such a small issue could bring a system to it's knees so thoroughly. More importantly I wonder if there is something I can do to prevent such things from happening to me or any of my users in the future, other than preemptively giving my applications permission in the firewall.
I had wondered if there is something unique to my application that was causing problems. I even tried creating a new application with the same UI but absolutely no logic - just a window with a few controls added that did nothing - but encountered the same freezing issue when running it. However, the application didn't freeze my system every time. Maybe it comes down to luck of timing - I was able to see the Comodo confirmation dialog sometimes and could give permission and continue.
If it is just a luck of the timing thing, I would think I would have applications freezing my system left, right and center. Maybe I don't use many apps that are built on WPF, but I use Visual Studio and it is I believe. I don't recall VS shutting down my system like this (except a few times when I tried to debug my own application). I can't swear to it, but it may be that I got lucky and granted full access to Visual Studio the first time I ran it so I never had a chance to experience this issue afterwards...
For you WPF developers, do you run into this sort of issue often in the wild?
So using the following diagram:
You can see that the only time when anything breaks is when I use ClickOnce in Windows 10, however the notifications work perfectly fine if I run it directly from the exe. When I run it using ClickOnce using the console I can see the same methods get hit in the console but the notifications don't show up. I have tried to get this fixed for a very long time now with no avail.
The click once is deployed to a network share. The ClickOnce notifications work fine on Windows 8. I have absolutely no idea what could be causing this.
So got into discussion with someone I know at Microsoft and it looks like in the latest version (that he said should be released somewhere in November 2015) should contain the fix for this issue.
Waiting it out and hopefully the fix comes, if not I will contact him again and see how things are going as I would say this is a really bad problem.
I am working on a Windows Phone 8.1 application. I am about a month into the project and have seen little to no issues with what I have written so far.
I decided to do some testing on the application without running it through the VS 2013 debugger. Now, for some reason, the app crashes before it gets to the first screen. I get no exceptions or messages whatsoever(I am using Raygun for error logging).
I am using async methods throughout(some async void, others async Task), but all of this works when debugging.
The main thing that would help, is to get some sort of error message. I've been reduced to commenting out sections of code, but ultimately this is getting me nowhere because it seems when I think I've found the issue, I get another crash further down into the code.
At one point, I found an issue with calling: ListView.UpdateLayout(). I commented this out and the app would run properly no crashes. I then un-commented some code further down and now it's crashing again.
If anyone knows of a way to get exceptions from the phone or if someone has experienced this issue before, any help would be greatly appreciated. I can provide any further information that is needed.
UPDATE:
I think I have narrowed the issue down to Sqlite.NET. I am using Sqlite.Net for WinRT along with an extension called SqliteNetExtensions. The particular statement is
DataContext.Context.Connection.Table<Message>().Where(m => m.ChannelID == channelID && m.ChannelID.Contains("C")).ToList();
If I comment this out, the app runs with no problems. This LINQ statement at most returns 100 records. I would not think that a 100 record SELECT statement could cause the app to crash, but it seems like the culprit. Any ideas on how to optimize Sqlite.NET?
UPDATE 2:
Finally figured it out! It was not SQLite at all. It was not my code at all. It was my phone. I am running a Nokia Lumia Icon. I had installed Rudy Huyn's Lockscreen Beta a few weeks back. It caused some issues when I uninstalled it but it wasn't related to my application. Today, I had my business partner install my app on his phone, he has the same model phone. The app was about 50x faster and did not crash. I restored my phone from factory and, lo and behold, it ran perfectly. So, pro tip: DO NOT INSTALL LOCKSCREEN BETA BY RUDY HUYN!!!
As an aside, I would take the time to ensure you always avoid using async void. It is well documented that async void is often a recipe for trouble.
There is a good article on the disadvantages shown here