Acknowledged
7 months ago

automatically resize the app icon instead of issueing the warning that the app icon will be resized

we all know the warning:

WARNING: vivoactive3: The launcher icon (40x40) isn't compatible with the specified launcher icon size of the device 'vivoactive3' (40x33). Image will be scaled to the target size.

is it really that bad that the icon will be resized? is it worthy of raising a warning and polluting the build output? 

to answer the question:

I don't think it's worth it.

In the new app I'm writing I went to the trouble to create resource overrides so that each device has the icon prebaked in it's preferred resolution. I had to create 47(!!!) resource override folders just to get rid of this warning.

What I'm doing manually (resizing the icon and saving it in it's specific resource folder) is nothing different than what the compiler does automatically if the icon is not in the desired icon size.

I think:

- this warning has no (/not much) benefit and should be removed.

 

peterdedecker
Parents
  • 7 months ago

    TL;DR the fact the launcher icons are so small (with so few pixels), and have so few available colours (on MIP devices) is actually an argument that automatic resizing is not always the best course of action (assuming the source isn't SVG).

    I understand that the warning is annoying though.

Comment
  • 7 months ago

    TL;DR the fact the launcher icons are so small (with so few pixels), and have so few available colours (on MIP devices) is actually an argument that automatic resizing is not always the best course of action (assuming the source isn't SVG).

    I understand that the warning is annoying though.

Children
No Data