-
Notifications
You must be signed in to change notification settings - Fork 56
ProGuard fails when using WorkManager #166
Comments
@Redth Any progress on this issue ? |
Adding these to your own proguard config seems to solve the problem
|
Yep, generally those errors just require adding proguard warnings. Thanks for posting that @ndastur ! |
@Redth the only thing I'd say is that the NuGET package should have the relevant proguard config included with it or at least something in the readme. |
We ship whatever proguard rules exist in the .aar so I’m not sure why these rules would be missed, but apparently it was. |
Thanks @Redth .. Yes, they do seem to be. I'm sure I've seen a build warning saying an expected proguard file is missing. Any idea about timeline on a fix? |
@Redth
|
Thanks, I wasn't aware the file wasn't being properly included. Looking at this. I see why it's happening (it's only inside |
Brilliant. Thank you. |
Are you kidding me ? This ticket was opened several months ago and the warning is the first line of the stack trace, how could you not be aware of that ?? Let me remind you that there are other issues concerning this package and waiting to be fixed: #204 #168 |
This should be fixed in this package update: https://www.nuget.org/packages/Xamarin.Android.Arch.Work.Runtime/1.0.0.3 Please let us know if this resolves the problem. |
issue is fixed |
No more warnings but I still need to add some rules to my proguard.cfg in order for it to work. |
Xamarin.Android Version (eg: 6.0):
9.2.0.5 (HEAD/292d27fa)
Operating System & Version (eg: Mac OSX 10.11):
Windows 10 1809 (OS build 17763.437)
Support Libraries Version (eg: 23.3.0):
28.0.0.1
Describe your Issue:
Adding Xamarin.Android.Arch.Work.Runtime NuGet package causes ProGuard to fail.
Steps to Reproduce (with link to sample solution if possible):
Sample solution
Include any relevant Exception Stack traces, build logs, adb logs:
Output from Visual Studio 2019:
The text was updated successfully, but these errors were encountered: