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

> is it really that bad that the icon will be resized?

Others might care if they are highly focused on aesthetics.

> 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.

In the case of this specific warning, the aspect ratio of the provided icon (square) isn't even the same as the device's launcher icon aspect ratio (40:33). In this case, should the resource compiler crop the icon or shrink it to fit? I assume that the icon will be shrunk to fit, but will it still look good?

Maybe some devs would prefer an icon that makes full use of the available real estate.

IOW, they may not want their 40x40 icon to be shrunk down to 33x33, they may wish to create a bespoke icon that's exactly 40x33 (and looks as good as possible at that size).

> 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.

Some might use a different resizing algorithm than Garmin, or they might go to the trouble of crafting resolution-matched icons by hand. As noted above, they may also produce substantially different icons for different aspect ratios.

Especially with the small number of pixels we are talking about, automatic resizing may not work well in all cases.

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

I'd like to propose an alternate solution where Garmin introduces a flag to suppress this warning.

For that matter, maybe every compiler warning should have a corresponding flag which suppresses it.

> is it really that bad that the icon will be resized?

Others might care if they are highly focused on aesthetics.

> 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.

In the case of this specific warning, the aspect ratio of the provided icon (square) isn't even the same as the device's launcher icon aspect ratio (40:33). In this case, should the resource compiler crop the icon or shrink it to fit? I assume that the icon will be shrunk to fit, but will it still look good?

Maybe some devs would prefer an icon that makes full use of the available real estate.

IOW, they may not want their 40x40 icon to be shrunk down to 33x33, they may wish to create a bespoke icon that's exactly 40x33 (and looks as good as possible at that size).

> 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.

Some might use a different resizing algorithm than Garmin, or they might go to the trouble of crafting resolution-matched icons by hand. As noted above, they may also produce substantially different icons for different aspect ratios.

Especially with the small number of pixels we are talking about, automatic resizing may not work well in all cases.

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

I'd like to propose an alternate solution where Garmin introduces a flag to suppress this warning.

For that matter, maybe every compiler warning should have a corresponding flag which suppresses it.