-
I'm seeing this exception logged in production since updating an app with a redesign and an update from Xamarin Forms 5.0.0.2012 to 5.0.0.2244.
It's affecting so far about 1% of Android users, causing a crash, and I'm unable to reproduce it because it seems to crash after a few seconds and only some of the time. The first page that's displayed is a CarouselView with a few images for onboarding, but none of them exceed a couple of hundred KB, so it doesn't explain the error. Any ideas what I could try to work out what's going on? In the stack trace (below) it mentions ShellFlyoutRenderer, but I'm not using a flyout, only a tab bar, which is weird. Full stack trace from App Center
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
I'm not convinced think this is a bug on our side, it mentions it tries to load a 115 megabyte image, so somehow users can end up doing that. Do you let people pick images or something like that? It is weird that it mentions the flyout... You do use Shell, just not the flyout? |
Beta Was this translation helpful? Give feedback.
-
I had to use a drawable-xxhdpi folder for an image that was being displayed. Originally the image was in the drawable folder and Android was trying to scale it up by a ridiculous amount. |
Beta Was this translation helpful? Give feedback.
-
Hello all. I download a thumbnail dynamically into a temporary file and specify ImageSource like this:ThumbSources.Add(Xamarin.Forms.ImageSource.FromFile(thumbPath)); How can I specify 'xxdpi' option in my code to make Xamarin ImageView work again? |
Beta Was this translation helpful? Give feedback.
-
Just to add an additional detail to anyone stumbling here. This also occurs with static images in "drawable" and older API levels and can be triggered in emulators consistently. For example, a small 13kb PNG on API 33 device will work fine, but on API 26 for some reason the image is scaled insanely large. Moving the images into the mipmap folders is one solution, but requires a bit more work. Can also confirm that adding the android:anyDensity property to the manifest does indeed work around the issue, though it could have side effects.
|
Beta Was this translation helpful? Give feedback.
I had to use a drawable-xxhdpi folder for an image that was being displayed. Originally the image was in the drawable folder and Android was trying to scale it up by a ridiculous amount.