-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the Review work for r8 shrinker and Linker set to “Link All” #9
Comments
Just verified that currently, the package crashes during runtime without a proguard file as shown in #10 @PatGet is there a way we can change the library to prevent users from having to add those lines to the proguard? cc: @AntvissMedia |
Seems like I could add a proguard.txt to the nuget just like dotnet/android#4449 (comment) mentions for the Xamarin.Android.Support.v7.AppCompat nuget package. Let me have a look... |
Can you please test https://www.nuget.org/packages/PlayCore/1.8.0.1-beta? I used your branch, uncommented the 3 lines from the proguard.txt and it still worked. But give it a try yourself please. |
@saamerm have you been able to test? |
Hmmm it didn't work unfortunately. It acted just like it does when its locally built. It didn't crash the app, but it didn't show the UI this time either |
Your "local" proguard worked just fine, the same proguard from the nuget made it not crash but work differently? That is strange. |
Are your changes in this repo? Could you please add them so I can retest in both ways, using the nuget and the library code itself |
Pushed the changes just now. |
Alright so I retested with a newer Visual Studio for Mac install, I was having issues with the older one. I tested the behaviour, if you just build the sample in dx, link none, and as before it works well. Apart from that I tested the following 4 scenarios: Installing from VS for MacNo nuget, just the library Using the NuGet package. Installing from Internal App SharingUsing the NuGet package.
|
Not sure why the library wouldn't work, maybe, we need to fix the sample. Were you able to test it and it worked for you? We also need to add this to the proguard |
I concentrated only on the startup part (which already crashed and that was fixed) so I did not test review functionality with my app. I checked the native SDK ZIP File and it comes with a handfull of proguard files. I guess i need to include all the rules. I still find it strange that the "3 Lines ProGuard" in the App directly works, in the Nuget not, while changing behaviour. I would have expected that it has the same result or also a NoSuchMethodError . |
I don´t get it to work on my site and have not enough time for dig deeper into how proguard and Nuget work for now. |
Sure no worries! Yeah let’s merge that in and I’ll try to take a stab at it @PatGet |
We still need to update the README to talk about the proguard stuff though |
Haven’t been able to figure this out yet. Spoke with Tomasz (www.Twitter.com/Cheesebaron), maintainer of multiple nuget packages (MVVMCross) with millions of downloads, who said that it’s not possible. |
Thanks @saamerm . I talked with Jonathan too, also with Jon Douglas. Both said it should work in theory. But it doesn´t and at least for me it has no priority right now. Will keep the issue open. |
When the linker settings is set to ‘Link All’, occasionally libraries will stop working.
We need to verify that the review works when a developer sets their Android project to Link All.
If it doesn’t work, let’s figure out a solution to the problem.
The text was updated successfully, but these errors were encountered: