Xamarin.Forms' Android doesn't compile with R8/ProGuard active in Release mode

[agharium]

Describe the bug
Xamarin.Forms' Android doesn't compile with R8/ProGuard active in Release mode.

To Reproduce
Steps to reproduce the behavior:

1. Activate R8/ProGuard with plugin installed and try to compile.

Expected behavior
Successful compilation.

Platform:

• OS: Windows 10
• Visual Studio 2019

Smartphone:

• Device: Tested on Emulator and Samsung A5 2017
• OS: Android
• Version 9.0 and 8.0, respectively

Additional context
Error when R8 active: Compilation can't be completed because some library classes are missing.
Error when ProGuard active: "java.exe" exited with code 1

It builds normally when no code reducer is selected.
Haven't tested on Debug mode (where code reducer is useless).

[thudugala]

Please attach a sample project

[thudugala]

xamarin/AndroidSupportComponents#168

[agharium]

Sample

Also, I noticed that on Android Oreo, the icon doesn't get any color (not even the gray when no color is set). Any idea why? I've only been testing on Android 8 and 9.

Check this out:

Android 9 Pie:

Android 8 Oreo:

As I know, this color feature was added on API 21, right? Not sure though.. Also, the icon file is exactly the same on both.

This could be a thing on my physical device.. it's a Samsung A5 2017 with the brand modified Android system and things..

And, by the way, thanks for the plugin, it's pretty good. I've been testing and if everything runs smooth, I'll use it on production.

[GitBOUF]

HI! Does anyone has a solution or a workaround for this problem? Getting the same error in release mode, with code shrinker set to R8 and with Plugin.LocalNotification version 5.0.0 or 5.0.1.
More specifically, the following class is missing: androidx.paging.PositionalDataSource

EDIT: Only way I've found to compile was by adding the following to proguard.cfg:
-keep class androidx.paging.PositionalDataSource { *; }
-dontwarn androidx.paging.PositionalDataSource
But it crashes the app instantly on launch, so not a workaround sadly

[thudugala]

@GitBOUF please add comment to issue #72

[thudugala]

Has a solution in #72