UWP renderer crashes if HTTP image cannot be found
See original GitHub issueIf an image can’t be found, like bad HTTP link or anything, the UWP renderer crashes uncatchably and crashes the parent app.
Repro payload
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "0.5",
"body": [
{
"type": "Image",
"url": "http://adaptivecards.io/assets/Closed%20bug%2092x92.png",
"size": "medium"
}
]
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
UWP, my app crashes for the image path when built , but ...
I'm creating a UWP that receives the image path from a static class. It works fine when I'm debugging it, but when built,...
Read more >[Visual Studio 2019 version 16.10][UWP][Xamarin] Runtime ...
This is a stowed exception, which means that there's a stored callstack and exception in that. The next time it crashes on your...
Read more >Resolved issues in Windows 11, version 21H2
Find information on recently resolved issues for Windows 11, version 21H2. To find a specific issue, use the search function on your browser...
Read more >UWP Player settings
To access the Universal Windows Platform (UWP) Player settings, go to Edit > Preferences > Project Settings > Player from the main menu...
Read more >Common Issues
Web Guides. Common Issues. This article lists some of the most common issues you might encounter while integrating PSPDFKit for Web. Styling Issues....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue is popping up more and more frequently. There are a few corner cases that are not captured with Andrew’s fix, such as:
I’m working on top of Andrew’s changes to address these issues. We have discussed a rework on how we handle image downloads, but that will require more comprehensive code changes. For now I’m patching our existing image downloader so that if one of this issues is present, the card won’t be rendered at all. It’s not ideal behavior, but I belive it’s the best thing we can do for now to fix a lot of the issues our consumers have been reporting.
Nice! Agreed, we can always add a new method like RenderWithErrorInfo or something that will provide a half-rendered card with error info about failed images/etc. For now just failing completely is good enough for our existing scenarios.