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
[Authenticator] The library should declare the needed consumer proguard rules #2797
Comments
This appears to be coming from the underlying Amplify library, not from Authenticator. Authenticator does not use push notifications. Transferring the issue there. |
Hi @pmellaaho, I've looked at this report and have been unable to reproduce this issue. In my sample app, I have the following Amplify dependencies:
I have minify enabled and have the default empty proguard rules:
Yet I'm able to build and minify without issue. Can you provide any more details that would suggest the library is at fault? |
Hello, thanks for looking into this.
I'm not sure which changes in my code has made the build warning to go away but I'm not seeing it anymore either. I have to return to this subject if the problem appears later again. |
Before creating a new issue, please confirm:
Which UI component?
Authenticator
Gradle script dependencies
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
When I'm doing a release build of my App that uses Amplify UI I get the following:
> Task :app:minifyReleaseWithR8 AGPBI: {"kind":"warning","text":"Missing class kotlinx.parcelize.Parcelize (referenced from: com.amplifyframework.notifications.pushnotifications.NotificationContentProvider$FCM and 2 other contexts)","sources":[{}],"tool":"R8"}
I can get around this by including the following in my proguardrules.pro
-dontwarn kotlinx.parcelize.Parcelize*
But the needed rules should really come with the library
Reproduction steps (if applicable)
No response
Code Snippet
// Put your code below this line.
Log output
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: