1. 23 Mar, 2017 1 commit
    • Chris Bracken's avatar
      Build Flutter app as a framework on iOS (#8971) · 0ee3f57a
      Chris Bracken authored
      **THIS IS A BREAKING CHANGE.** See below for migration steps for
      existing projects.
      
      Previously, Flutter app code was built as a raw dylib on iOS.  Dynamic
      libraries outside of a framework bundle are not supported on iOS, except
      for the system Swift libraries provided by Xcode.
      
      See:
      https://developer.apple.com/library/content/technotes/tn2435/_index.html#//apple_ref/doc/uid/DTS40017543-CH1-TROUBLESHOOTING_BUNDLE_ERRORS-EMBEDDED__DYLIB_FILES
      
      * Migrates Xcode build from app.dylib to App.framework
      * Migrates flutter create template
      * Migrates example projects
      
      Migration steps for existing projects
      =====================================
      
      The following steps should be taken from the root of your Flutter
      project:
      
      1. Edit `ios/.gitignore`: add `/Flutter/App.framework` on a new line.
      2. In the Xcode project navigator, remove `app.dylib` from the Flutter
         folder. Delete this file from the `ios/Flutter` directory in your project.
      3. Run a build to generate `ios/Flutter/App.framework`. From the command
         line, run `flutter build ios`. If you have not configured app signing
         in Xcode, an alternative method is to open the simulator, then run
         `flutter run -d iP`.
      4. In the Xcode project navigator, select the `Runner` project. In the
         project settings that are displayed in the main view, ensure that the
         `Runner` target is selected. You can verify this by exposing the
         sidebar using the [| ] icon in the upper-left corner of the main
         view.
      5. Select the *General* tab in the project settings. Under the
         *Embedded Binaries* section, click '+' to add `App.framework`. In the
         sheet that drops down, click the *Add Other...* button. Navigate to
         the `ios/Flutter` directory and select `App.framework`. Click *Open*.
         In the sheet that drops down, select *Create folder references*, then
         click *Finish*.
      6. In the project settings, verify that `App.framework` has been added to the
         *Embedded Binaries* and *Linked Frameworks and Libraries* lists.
      7. In the Xcode project navigator, drag `App.framework` under the
         Flutter folder.
      8. In the Xcode project navigator, select `Flutter` then from the
         *File* menu, select *Add Files to "Runner"...*. Navigate to the
         `ios/Flutter` directory, select `AppFrameworkInfo.plist` and click
         the *Add* button.
      9. From the command line, in your project directory, run
         `flutter build clean`, then `flutter run`.
      
      At this point your project should be fully migrated.
      0ee3f57a
  2. 08 Mar, 2017 2 commits
  3. 07 Mar, 2017 2 commits
  4. 28 Feb, 2017 1 commit
  5. 21 Feb, 2017 1 commit
  6. 15 Feb, 2017 2 commits
  7. 14 Feb, 2017 1 commit
  8. 09 Feb, 2017 1 commit
  9. 07 Feb, 2017 1 commit
  10. 03 Feb, 2017 1 commit
  11. 01 Feb, 2017 2 commits
  12. 27 Jan, 2017 1 commit
  13. 24 Jan, 2017 1 commit
  14. 23 Jan, 2017 1 commit
    • Michael Thomsen's avatar
      Update IntelliJ template for new projects and existing samples (#7501) · 24f1b2ee
      Michael Thomsen authored
      * Disable 'Show Excluded' by default
      
      * Move .iml file inside .idea dir
      
      * Remove pub and build excludions as they are automatically set by the Dart plugin
      
      * Exclude .idea folder (new users will edit it through the IJ UI, not the file)
      
      * Move .iml files into .idea dir to be consistent with template changes
      
      * Add workspace.xml from new template to existing samples
      
      * Update current examples to match template changes for excluding folders
      
      * Add missing flutter.yaml to make sure there are no analysis errors
      
      * Add back .pub and build excludeFolder tags per https://github.com/flutter/flutter-intellij/issues/630#issuecomment-272887230
      
      * Remove workspace.xml from example per review feedback
      24f1b2ee
  15. 12 Jan, 2017 1 commit
  16. 07 Dec, 2016 1 commit
  17. 27 Nov, 2016 1 commit
  18. 14 Nov, 2016 1 commit
    • Dan Rubel's avatar
      Refactor flutter command exit code - part 3 of 3 (#6838) · 34e466f1
      Dan Rubel authored
      * Remove the workaround that pinned args to v0.13.6
      This reverts most of the changes in commit 6331b6c8
      * throw exception if exit code is not an integer
      * rework command infrastructure to throw ToolExit when non-zero exitCode
      * convert commands to return Future<Null>
      * cleanup remaining commands to use throwToolExit for non-zero exit code
      * remove isUnusual exception message
      * add type annotations for updated args package
      34e466f1
  19. 08 Nov, 2016 1 commit
  20. 01 Nov, 2016 1 commit
  21. 15 Oct, 2016 1 commit
  22. 14 Oct, 2016 1 commit
  23. 13 Oct, 2016 2 commits
  24. 07 Oct, 2016 2 commits
  25. 26 Sep, 2016 1 commit
    • Chris Bracken's avatar
      Update examples to Xcode 8 recommended settings · 71b65e32
      Chris Bracken authored
      As of Xcode 7, Apple recommends setting the bundle identifier in the
      PRODUCT_BUNDLE_IDENTIFIER build variable and setting CFBundleIdentifier
      to that variable in Info.plist.
      
      As of Xcode 8, CLANG_WARN_INFINITE_RECURSION and CLANG_WARN_SUSPICIOUS_MOVE
      are recommended settings.
      71b65e32
  26. 23 Sep, 2016 1 commit
  27. 05 Aug, 2016 2 commits
  28. 20 Jul, 2016 1 commit
    • Devon Carew's avatar
      Hello services run (#4969) · 57b76a05
      Devon Carew authored
      * making flutter run work with gradle
      
      * locate android studio
      
      * add test for settings
      
      * review comments
      57b76a05
  29. 07 Jul, 2016 1 commit
  30. 06 Jul, 2016 1 commit
  31. 16 May, 2016 1 commit
    • Ian Hickson's avatar
      Make it possible to run tests live on a device (#3936) · 32527017
      Ian Hickson authored
      This makes it possible to substitute 'flutter run' for 'flutter test'
      and actually watch a test run on a device.
      
      For any test that depends on flutter_test:
      
      1. Remove any import of 'package:test/test.dart'.
      
      2. Replace `testWidgets('...', (WidgetTester tester) {`
            with `testWidgets('...', (WidgetTester tester) async {`
      
      3. Add an "await" in front of calls to any of the following:
          * tap()
          * tapAt()
          * fling()
          * flingFrom()
          * scroll()
          * scrollAt()
          * pump()
          * pumpWidget()
      
      4. Replace any calls to `tester.flushMicrotasks()` with calls to
         `await tester.idle()`.
      
      There's a guarding API that you can use, if you have particularly
      complicated tests, to get better error messages. Search for
      TestAsyncUtils.
      32527017
  32. 10 May, 2016 1 commit
  33. 09 May, 2016 1 commit