-
Notifications
You must be signed in to change notification settings - Fork 247
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
Flutter 3.24 build apk issue #5542
Comments
Hi @KishanD24, thank you for taking the time to submit this issue. We will look into it and provide updates when we can. |
I have the same problem, changing the |
@passsy @KishanD24 would you please provide reproduction steps so that we can investigate this issue. thanks. |
We discovered that is was caused by JDK 21. Downgrading to JDK 17 resolved the issue |
Ok I try with lower jdk support.
…On Tue, 15 Oct 2024, 3:23 pm Pascal Welsch, ***@***.***> wrote:
1. Create a flutter project
2. add amplify_auth_cognito
3. Build the android version
We discovered that is was caused by JDK 21. Downgrading to JDK 17 resolved
the issue
—
Reply to this email directly, view it on GitHub
<#5542 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXLMEYS6B6K66REJUTSU5FTZ3TQ2HAVCNFSM6AAAAABP3GAL6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGQZDQMJWGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Description
Development environment
amplify packages reproduction steps |
@passsy @KishanD24 @alishawnee thanks for providing the info. we will look into this issue and get back to you with any updates. |
@passsy @KishanD24 @alishawnee I was not able to reproduce this issue following the steps. I get the below error if I do not update android platform settings as described here.
After following the android platform setup I was able to build the android app and run it sucessfully. |
Hello I solved that bug by updating my java version to 11
Now it's working fine in java 11.
If you want to close that issue then you can close it
Thank you for your response.
…On Thu, 17 Oct 2024, 4:00 am NikaHsn, ***@***.***> wrote:
@passsy <https://github.com/passsy> @KishanD24
<https://github.com/KishanD24> @alishawnee <https://github.com/alishawnee>
I was not able to reproduce this issue following the steps. I get the below
error if I do not update android platform settings as described here
<https://docs.amplify.aws/flutter/start/platform-setup/#android>.
Execution failed for task ':app:processDebugMainManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 21 cannot be smaller than version 24 declared in library [:amplify_auth_cognito] /Users/nikaws/gh-issues/gh5542/build/amplify_auth_cognito/intermediates/merged_manifest/debug/AndroidManifest.xml as the library might be using APIs not available in 21
Suggestion: use a compatible library with a minSdk of at most 21,
or increase this project's minSdk version to at least 24,
or use tools:overrideLibrary="com.amazonaws.amplify.amplify_auth_cognito" to force usage (may lead to runtime failures)
After following the android platform setup I was able to build the android
app and run it sucessfully.
—
Reply to this email directly, view it on GitHub
<#5542 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXLMEYVZYKOXLKL5OM6EZALZ33SHTAVCNFSM6AAAAABP3GAL6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJYGA3TOMZXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
thanks for the reply and glad that the issue is resolved. as mentioned in our docs Amplify Flutter supports minimum java version 17 when targeting android platform. |
Description
amplify_auth_cognito Having issue win32 and 2nd is as below issue
i fixed win32 by adding
dependency_overrides:
win32: ^5.6.0
but still having issue in flutter 3.24 as below
Execution failed for task ':amplify_analytics_pinpoint:compileReleaseJavaWithJavac'.
Categories
Steps to Reproduce
Just run in flutter 3.24
Screenshots
Platforms
Flutter Version
3.24.3
Amplify Flutter Version
2.4.1
Deployment Method
Amplify Gen 2
Schema
No response
The text was updated successfully, but these errors were encountered: