- 23 Mar, 2017 3 commits
-
-
Mikkel Nygaard Ravn authored
-
Mikkel Nygaard Ravn authored
-
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.
-
- 22 Mar, 2017 12 commits
-
-
Kevin Moore authored
* Teach flutter_tools to populate PUB_ENVIRONMENT Will allow telemetry reporting on pub.dartlang.org once flutter moves to 1.23.0-dev.10.0 * review changes
-
Collin Jackson authored
* Improvements to CircleAvatar default color (for codelab) * use a transparent white instead of a solid one * Fix analyzer errors * fix tests
-
Michael Goderbauer authored
-
Michael Goderbauer authored
* Print error message if a package is skipped during DevFS sync. * review comments * more review comments * fix test
-
Michael Goderbauer authored
-
Ian Hickson authored
-
Hans Muller authored
-
Jakob Andersen authored
-
Jakob Andersen authored
* Remove unnecessary Android SDK checks. * Remove unused accessors, skip replay test.
-
Sarah Zakarias authored
* Refactor platform_services sample * removed exception
-
Sarah Zakarias authored
-
Michael Thomsen authored
* Revert "use color.shadeXxx instead of color[Xxx] (#8932)" This reverts commit 578ca0a2. * Revert "add missing const keyword (#8931)" This reverts commit fac2fac1. * Revert "Make min/max fling velocity and min fling distance ScrollPhysics properties (#8928)" This reverts commit dac80aac. * Revert "Defer to operating system for whichAll (#8921)" This reverts commit 14933de9. * Revert "Update gradle wrapper and build-tools version for flutter create. (#8914)" This reverts commit deb71cc6.
-
- 21 Mar, 2017 7 commits
-
-
Alexandre Ardhuin authored
* use color.shadeXxx instead of color[Xxx] * remove calls to .shade500 on MaterialColor * remove calls to .shade200 on MaterialAccentColor * fix test
-
Alexandre Ardhuin authored
-
Hans Muller authored
-
Michael Goderbauer authored
The old `whichAll` implementation was not considering different extensions for executables on Windows. By defering to OS-built-in tools we avoid implementing it. Fixes #8882.
-
asaarnak authored
* Update gradle wrapper and build-tools version. Tested manually by "flutter create" with Idea "flutter run" and from android studio "run" android app. * Update com.android.tools.build to 2.3.0
-
Adam Barth authored
This patch prepares us to remove InputValue in favor of TextEditingValue.
-
Michael Goderbauer authored
* Avoid downloading artifacts twice * Don't update cache before `flutter upgrade` is executed (`flutter upgrade` might bump the engine version) * Don't update cache twice during `flutter precache` Fixes #8249. * add test
-
- 20 Mar, 2017 15 commits
-
-
Adam Barth authored
Fixes #8235
-
Adam Barth authored
Fixes #8794
-
Adam Barth authored
Fixes #8519
-
Adam Barth authored
The latter is the proper spelling. Fixes #8883
-
Ian Hickson authored
We keep breaking --watch because we don't test it.
-
Jason Simmons authored
-
Jason Simmons authored
-
Adam Barth authored
Fixes #7520
-
Sarah Zakarias authored
-
Adam Barth authored
Fixes #4017
-
Adam Barth authored
Previously they tried to compute an integer target end index, but integers can't represent infinity. Now we use null to represent infinity. Also, fix some similar issues with grids. Fixes #8398
-
Adam Barth authored
Fixes #7503 Fixes #8870
-
-
Jakob Andersen authored
-
Jakob Andersen authored
* Remove legacy .apk build. Print out an error message telling the user to upgrade the project if it's not Gradle-based. Removed all the obvious traces of the legacy build. Added support for Dart VM kernel snapshots in Gradle builds. Fixed Android installs to verify that the app is actually installed, and not just rely on the presence of the .sha1 file.
-
- 19 Mar, 2017 3 commits
-
-
Adam Barth authored
Fixes #4301
-
David Yang authored
The recommended minimum tappable area is actually 44.0pt according to the [iOS Human Interface Guidline](https://developer.apple.com/ios/human-interface-guidelines/visual-design/layout/). > Provide ample spacing for interactive elements. Try to maintain a minimum tappable area of 44pt x 44pt for all controls. I've also added an override to allow for flexibility in situations where designers get naughty and have a desire to make everything super small.
-
Zachary Anderson authored
-