Skip to content

Boiletplate Android Manifest misses required attributes #1006

Closed

Description

@stevenroose

After trying to publish a Flutter-created app to Google Play, it noticed me that some required pieces were missing from the AndroidManifest.xml file.

  • the android:versionCode and android:versionName attributes in <manifest>
  • android:icon in <application>, although this attribute requires the presence of an actual icon drawable

Activity

  1. devoncarew commented on Dec 21, 2015

    @devoncarew
    Contributor

    @stevenroose, the code to generate the manifest file lives here: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/commands/init.dart#L226 if you want to try your hand at a PR. I'm less familiar with those constants and what they should default to.

  2. stevenroose commented on Dec 21, 2015

    @stevenroose
    Author

    I'm pretty new to Android dev too, but I'll see. Thing is that for me to
    fix the icon part, I need to actually upload an icon or else the app cant
    run. Should I create a dummy Flutter logo-based icon?

    On Mon, Dec 21, 2015 at 8:12 PM, Devon Carew [email protected]
    wrote:

    @stevenroose https://github.com/stevenroose, the code to generate the
    manifest file lives here:
    https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/commands/init.dart#L226
    if you want to try your hand at a PR. I'm less familiar with those
    constants and what they should default to.

    —
    Reply to this email directly or view it on GitHub
    #1006 (comment).

  3. devoncarew commented on Dec 21, 2015

    @devoncarew
    Contributor

    I think we should have an icon in there, if that's what's needed to to publish the sample. You could probably either just add a comment to the manifest file, or add an icon to the generated app, based off the flutter logo.

  4. eseidelGoogle commented on Dec 21, 2015

    @eseidelGoogle
    Contributor

    I'm also not 100% sure if the flutter apk command signs with the correct key, which you definitely want to do before publishing. On my system it uses the chromium dev keys, presumably on a non-dev system it would have prompted for personal android signing keys? I suspect that @jason-simmons thought of this when he wrote flutter apk, i just haven't tested proper signing personally.

    It looks like flutter apk is hardcoded to teh chromium signing key:
    https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/commands/apk.dart#L146

    You don't want to publish with that key. :( We will need to fix the command.

  5. abarth commented on Dec 21, 2015

    @abarth
    Contributor

    On my system it uses the chromium dev keys, presumably on a non-dev system it would have prompted for personal android signing keys?

    I believe it always uses the Chromium dev key. Would you be willing to file a bug about improving the command?

  6. sethladd commented on Dec 21, 2015

    @sethladd
    Contributor

    We will need to fix the command.

    Should we open a new issue?

  7. eseidelGoogle commented on Dec 21, 2015

    @eseidelGoogle
    Contributor

    Filed #1010

  8. eseidelGoogle commented on Dec 21, 2015

    @eseidelGoogle
    Contributor

    To answer the earlier question, @stevenroose, we should include a default icon. I recommend using the simple flutter one from material_gallery (and then we should give material_gallery a nicer one):
    https://github.com/flutter/flutter/tree/master/examples/material_gallery/apk

  9. added this to the milestone on Jan 16, 2016
  10. modified the milestones: Hackathon, on Jan 26, 2016
  11. eseidelGoogle commented on Jan 26, 2016

    @eseidelGoogle
    Contributor

    We probably need this for the Hackathon. The initial flutter init flow needs to produce a working (and ideally store-compatible) app.

  12. stevenroose commented on Jan 26, 2016

    @stevenroose
    Author

    What hackathon when?? :)

  13. 1 remaining item

  14. stevenroose commented on Jan 26, 2016

    @stevenroose
    Author

    Bummer. Well, I'm curious. Flutter could indeed benefit from a huge
    documentation improvement. However boring to provide, it's inevitable for
    adoption.

    On Tue, Jan 26, 2016 at 2:37 AM, Eric Seidel [email protected]
    wrote:

    We're holding a flutter-team hackathon in mid march. Make sure that all of
    the folks who work on Flutter and its dependencies have written a flutter
    app themselves. :) You'll be seeing us make a large push for better
    developer experience, docs, onboarding, etc between now and then. Sorry we
    don't have any plans for a publicly hosted hackathon at this time.

    —
    Reply to this email directly or view it on GitHub
    #1006 (comment).

  15. eseidelGoogle commented on Jan 26, 2016

    @eseidelGoogle
    Contributor

    Please feel encouraged to file bugs against our documentation shortcomings. @qchong recently joined our project and is working explicitly on making sure we have a coherent technical writeups of flutter and how to use it. Other members of the team have slowly been adding more dartdocs to the code, which are generated by our builders and appear at https://docs.flutter.io immediately after they are landed in the repository.

  16. self-assigned this
    on Feb 12, 2016
  17. added a commit that references this issue on Feb 12, 2016
    0ae17bc
  18. github-actions commented on Sep 6, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  19. locked as resolved and limited conversation to collaborators on Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

platform-androidAndroid applications specifically

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions