Skip to content

Can't flutter install flavor to iOS device #98151

Closed
Closed
Can't flutter install flavor to iOS device#98151
Labels
r: solvedIssue is closed as solved

Description

@bradyt
bradyt
opened on Feb 9, 2022

Duplicate of #64856.

Flutter version is 2.10.0.

Project is configured with flavors for iOS, and build or run succeed, but install does not.

Reproduce is as follows:

> git clone https://github.com/flutter/flutter
> cd flutter/dev/integration_tests/flavors

Replace contents of pubspec.yaml with the following:

name: flavors

environment:
  sdk: ">=2.12.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_driver:
    sdk: flutter

Continue with the following:

> flutter build ios --flavor free
> flutter install -d 'iphone 14'

The Xcode project defines schemes: free, paid
You must specify a --flavor option to select one of the available schemes.

EDIT: links to repos mentioned in this comment and next one added for convenience:

Activity

  1. bradyt commented on Feb 9, 2022

    @bradyt
    bradyt
    on Feb 9, 2022
    Author

    The following steps are an alternative reproduce, using a repo with very similar structure as the integration test above, and notes to create it from scratch, that is, flutter create.

    > git clone https://github.com/bradyt/flutter-flavor-reproduce-steps
> cd flutter-flavor-reproduce-steps
> flutter build ios --flavor free
> flutter install -d 'iphone 14'

The Xcode project defines schemes: free, paid
You must specify a --flavor option to select one of the available schemes.

  2. bradyt commented on Feb 10, 2022

    @bradyt
    bradyt
    on Feb 10, 2022
    Author

    First searching the issue tracker, then searching the wider internet, with search terms like "flutter install scheme flavor ios", I may have some solution, trying a video on youtube.

    I found a way to recreate this breakage on a working app, at the associated example I found at https://github.com/Flutter-Explained/flavor_tutorial.

    In that repo, if I use Xcode to delete the third scheme "Runner" leaving schemes "cookie" and "coffee", I get the bug above.

    So my naive impression is that for those of us creating two schemes for flavors, we have to keep a third, the old Runner scheme, around.

    The author mentions in the youtube channel that they could have deleted the default configurations, but that also lead to errors, though I haven't tried yet to see if those are easily fixable.

  3. darshankawar
    added
    in triagePresently being triaged by the triage team
    on Feb 10, 2022

  4. darshankawar commented on Feb 10, 2022

    @darshankawar
    darshankawar
    on Feb 10, 2022
    Member

    @bradyt
    Although I didn't try the integration_test flavor example you shared above, I tried one of flutter's flavor example based on this article that has dev and prod flavors. Running the said command built and installed the dev version of the app on my iphone properly without any issues:

    dhs@Dhss-MacBook-Pro flavors_example % flutter build ios --flavor dev                             
Building com.nevercode.triage for device (ios-release)...
Found saved certificate choice "Apple Development: Darshan Kawar (AV76JL68FU)". To clear, use "flutter config".
Signing iOS app for device deployment using developer identity: "Apple Development: Darshan Kawar (AV76JL68FU)"
Running Xcode build...                                                  
 └─Compiling, linking and signing...                         5.0s
Xcode build done.                                            9.4s
Built /Users/dhs/Documents/NCFlutter/triage-examples/flutter_examples/flavors_example/build/ios/iphoneos/Runner.app.
dhs@Dhss-MacBook-Pro flavors_example % flutter install -d 21150b119064aecc249dfcfe05e259197461ce23
Installing com.nevercode.triage to Darshan's iphone...
Uninstalling old version...
dhs@Dhss-MacBook-Pro flavors_example %
  5. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Feb 10, 2022

  6. bradyt commented on Feb 10, 2022

    @bradyt
    bradyt
    on Feb 10, 2022
    Author

    Right the "Flutter Explained" example follows that blog article you linked.

    My understanding is that the integration test discards the original Runner scheme, and original configurations, and creates the two schemes and sets of matching configurations to replace.

    I get the sense that Flutter requires that original Runner scheme and configurations in order for flutter install to work.

    If that's correct, is it expected behavior that flavor/scheme usage must retain that Runner scheme? I found it interesting that it didn't seem to be needed for flutter run. I get the sense that someone deliberately did not want a requirement on the original Runner scheme, but didn't finish up ensuring it worked with flutter install.

  7. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Feb 10, 2022

  8. bradyt commented on Feb 10, 2022

    @bradyt
    bradyt
    on Feb 10, 2022
    Author

    Should we simply close issue? The issue as originally described seems solved. I don't know if my previous question about Runner scheme is really relevant to Flutter.

  9. darshankawar commented on Feb 10, 2022

    @darshankawar
    darshankawar
    on Feb 10, 2022
    Member

    Thanks, yes, closing based on above comment.

  10. darshankawar
    closed this as completedon Feb 10, 2022
  11. darshankawar
    added
    r: solvedIssue is closed as solved
    and removed
    in triagePresently being triaged by the triage team
    on Feb 10, 2022

  12. bradyt commented on Feb 11, 2022

    @bradyt
    bradyt
    on Feb 11, 2022
    Author

    @darshankawar Can you please provide the code example you ran described here?

    I tried one of flutter's flavor example based on this article that has dev and prod flavors.

    This way if I have more issues, we can all start from the minimal example you have, that should ideally work better than any of mine.

    Asking for source code that works with current Flutter, if possible.

  13. bradyt commented on Feb 11, 2022

    @bradyt
    bradyt
    on Feb 11, 2022
    Author

    Um, never mind, I think I finally got it. Not sure why I didn't wait a few more seconds for recent test.

    I think not only is it required to keep the Runner scheme, but the Runner scheme has to have a distinct bundle ID from each of the schemes, or else a flutter build ios --flavor dev && flutter install -d "iphone 14" will overwrite an install from the prod listing at TestFlight, rather than the install from the matching dev listing.

  14. bradyt commented on Feb 12, 2022

    @bradyt
    bradyt
    on Feb 12, 2022
    Author

    In other words, if the bundle ID of the prod scheme matches the bundle ID of the original Runner scheme, then locally building and installing the dev scheme will overwrite an install from the TestFlight listing for prod. That seems a little surprising, and something to be aware of.

    I've renamed the bundle ID for Runner as com.example.app.Runner, to be distinct from prod bundle ID, and things seem to be working better.

  15. github-actions commented on Feb 26, 2022

    @github-actions
    github-actionsbot
    on Feb 26, 2022

    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.

  16. github-actions
    locked as resolved and limited conversation to collaborators on Feb 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    r: solvedIssue is closed as solved

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions