You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to help fellow developers avoid the costly mistake that I made, so I am proposing this.
3.x breaks only the release (i.e. .Net Native) versions of UWP apps while the debug versions work just fine. Since the release version takes quite a few mintues to build, it may be rarely tested. 3.x causes the release version of a UWP app to crash in a weird way, making it hard to debug. The release version crashes immediately after the splash screen. VS displays the message "The target process aborted before activation completed", but nothing in the debug output window.
I happened to test the release version of an app yesterday after making lots of changes, including updates of over two dozen NuGet packages. I was determined to find a clue without reverting all the changes, and I ended up spending a whole day on this only to give up in the end. I reverted all the changes, and updated NuGet packages one by one with a test of the release version, which takes minutes to build, after each update, and found the culprit.
I doubt I will forget this and update SkiaSharp by mistake again. I wonder if other developers may make this costly mistake.
I used to test only the debug versions of UWP apps and thought Microsoft Store would detect such crashes for submitted apps. Out of curiosity, I submitted an app with this issue, and Microsoft Store published it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to help fellow developers avoid the costly mistake that I made, so I am proposing this.
3.x breaks only the release (i.e. .Net Native) versions of UWP apps while the debug versions work just fine. Since the release version takes quite a few mintues to build, it may be rarely tested. 3.x causes the release version of a UWP app to crash in a weird way, making it hard to debug. The release version crashes immediately after the splash screen. VS displays the message "The target process aborted before activation completed", but nothing in the debug output window.
I happened to test the release version of an app yesterday after making lots of changes, including updates of over two dozen NuGet packages. I was determined to find a clue without reverting all the changes, and I ended up spending a whole day on this only to give up in the end. I reverted all the changes, and updated NuGet packages one by one with a test of the release version, which takes minutes to build, after each update, and found the culprit.
I doubt I will forget this and update SkiaSharp by mistake again. I wonder if other developers may make this costly mistake.
I used to test only the debug versions of UWP apps and thought Microsoft Store would detect such crashes for submitted apps. Out of curiosity, I submitted an app with this issue, and Microsoft Store published it.
Beta Was this translation helpful? Give feedback.
All reactions