Skip to content
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

Note: /Users/administrator/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_mailer-2.0.0/android/src/main/java/com/dataxad/flutter_mailer/FlutterMailerPlugin.java uses or overrides a deprecated API #43

Closed
Development4A opened this issue Aug 19, 2021 · 9 comments

Comments

@Development4A
Copy link

error message on "flutter build appbundle"

Because http >=0.13.0 depends on http_parser ^4.0.0 and firebase_auth_web <0.4.0-1.0.nullsafety.0 depends on http_parser ^3.1.3, http >=0.13.0 is incompatible with firebase_auth_web <0.4.0-1.0.nullsafety.0.
And because firebase_auth >=0.15.2 <0.17.0-dev.1 depends on firebase_auth_web ^0.1.1, http >=0.13.0 is incompatible with firebase_auth >=0.15.2 <0.17.0-dev.1.
So, because easy_list_pro depends on both http ^0.13.0 and firebase_auth ^0.15.3, version solving failed.

@taljacobson
Copy link
Owner

Seems like it a dependency issue with http ^0.13.0 and firebase_auth ^0.15.3 requiring Different major versions of http_parser.

Try to update those packages.

As with the android deprecated APIs, it should still compile.

@Development4A
Copy link
Author

Updated the two and got a different error for firebase_core.

Did:
dependency:
firebase_core: ^1.5.0
dependency_overrides:
firebase_core: ^0.4.0

Took the above out and I get:
Note: /Users/administrator/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_mailer-2.0.0/android/src/main/java/com/dataxad/flutter_mailer/FlutterMailerPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':app:validateSigningRelease'.

Keystore file not set for signing config release

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 48s
Running Gradle task 'bundleRelease'...
Running Gradle task 'bundleRelease'... Done 49.0s
Gradle task bundleRelease failed with exit code 1
administrator@iMac easy_list_pro % flutter build appbundle Xlint:deprecation
Target file "Xlint:deprecation" not found.
administrator@iMac easy_list_pro % flutter build appbundle -Xlint:deprecation
Could not find an option with short name "-X".

The ios version is in the App store.
I do not know what I am doing.

@Development4A
Copy link
Author

Tried to build as an APK instead of APPBUNDLE. the Java message warning disappears but the "app:validateSigningRelease" is still there so it will not build.

@taljacobson
Copy link
Owner

seems to be a android signing issue.

is this the first time building for release?

try following this https://flutter.dev/docs/deployment/android#signing-the-app

@Development4A
Copy link
Author

I have another Flutter App that I had no problem with compiling and send to the Play Store.

@Development4A
Copy link
Author

I created a new signature file. No change.

@Development4A
Copy link
Author

I tried from the internet: “flutter build appbundle --target-platform android-arm,android-arm64,android-x64”. No Java error but here is still the “app:validateSigningRelease” error, so no build.

@Development4A
Copy link
Author

I tried: flutter build appbundle --debug --verbose I do not see an error message at the end of the report. No "release" file at [project]/build/app/outputs/bundle/release/app.aab There is no release folder.

@Development4A
Copy link
Author

I found the problem. I misspelled key.properties.

Sorry about taking up so much space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants