- 28 Nov, 2017 1 commit
-
-
xster authored
-
- 15 Aug, 2017 1 commit
-
-
xster authored
* Add iOS template * Android * Let the engine reset the theme without the activity knowing * Small tweak * Replace assets with different vectors * Let the template hookup have no actual image assets * Add back placeholder assets with 1px transparent pngs * Fix drawable xml * clean up an extraneous line in the storyboard xml
-
- 24 May, 2017 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 19 May, 2017 1 commit
-
-
Collin Jackson authored
-
- 18 May, 2017 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 16 May, 2017 1 commit
-
-
Collin Jackson authored
Fixes #10106
-
- 09 May, 2017 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 04 May, 2017 1 commit
-
-
xster authored
* Remove all initial cocoapod traces from flutter create except Podfile * Make updateXcodeGeneratedProperties parameters named * review notes
-
- 24 Apr, 2017 1 commit
-
-
Michael Thomsen authored
-
- 21 Apr, 2017 1 commit
-
-
Michael Thomsen authored
* Add Pods cache dir to ios/.gitngnore * Add missing ending newlines
-
- 10 Apr, 2017 1 commit
-
-
Jakob Andersen authored
Added a PluginRegistry to the new project template. The registry files will be automatically updated at build time to register the native plugins. Fixes #7814.
-
- 05 Apr, 2017 1 commit
-
-
Collin Jackson authored
-
- 30 Mar, 2017 1 commit
-
-
Jakob Andersen authored
Plugin projects are created by running `flutter create --plugin <name>`. An example app is also created in the plugin project, using the normal 'create' template, which has been modified to allow for conditional plugin code. Modified the android package name to match package naming conventions (all lower-case, and must match the directory name).
-
- 23 Mar, 2017 2 commits
-
-
Jakob Andersen authored
Go through all packages brought in by pub, and write the name and path of every one that is a flutter plugin into .flutter-plugins. In android/settings.gradle and ios/Podfile, read in .flutter-plugins, if that file exists. The Android / iOS code from the plugins is automatically added as dependencies of the native code of the app.
-
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.
-
- 07 Mar, 2017 3 commits
-
-
Chris Bracken authored
Update templates and example Xcode project files to indicate they've been tested for Xcode 8.3 compatibility.
-
Chris Bracken authored
This matches the default for Runner.xcodeproj and fixes a linker warning when the two projects use different values.
-
Chris Bracken authored
Add 20x20 notification icons. Remove unused 76x76 (3x scale) icon. Fixes warnings for missing/unused icon assets in Xcode 8.2.x
-
- 06 Mar, 2017 1 commit
-
-
Chris Bracken authored
This prevents project re-validation on initial Xcode launch.
-
- 09 Feb, 2017 1 commit
-
-
Chris Bracken authored
-
- 07 Feb, 2017 1 commit
-
-
Chris Bracken authored
* Support thinning iOS frameworks to supported architectures When building against frameworks that are distributed as multi-architecture fat binaries, we want to strip the frameworks we distribute down to only the architectures specified in $ARCHS. This patch adds: * The ability to specify commands to xcode_backend.sh (if none is specified, run BuildApp for backward compatibility). * A 'thin' command that invokes lipo to thin down the distributed as described above. * Add framework thinning step to iOS build Invokes xcode_backend.sh thin on the build application. * Limit architectures to arm64 in Xcode template Flutter does not yet support armv7 iOS devices. Limit the $ARCHS build variable to arm64 until then.
-
- 03 Feb, 2017 1 commit
-
-
Chris Bracken authored
On iOS, generate a FlutterAppDelegate subclass for the application delegate. This avoids touchesBegan:withEvent boilerplate to handle status bar taps.
-
- 02 Feb, 2017 1 commit
-
-
Chris Bracken authored
By default, pass status bar taps to the root view controller in generated Flutter apps. Developers should customise as necesary if they later create one or more alternate FlutterViewControllers that they'd like to forward these to.
-
- 01 Feb, 2017 1 commit
-
-
Chris Bracken authored
-
- 28 Nov, 2016 1 commit
-
-
Collin Jackson authored
-
- 26 Sep, 2016 1 commit
-
-
Chris Bracken authored
-
- 18 Aug, 2016 1 commit
-
-
Seth Ladd authored
-
- 16 Aug, 2016 1 commit
-
-
Collin Jackson authored
-
- 15 Aug, 2016 1 commit
-
-
Collin Jackson authored
-
- 08 Aug, 2016 1 commit
-
-
Devon Carew authored
-
- 05 Aug, 2016 3 commits
-
-
Chinmay Garde authored
* Update examples to lower the deployment target on iOS.
-
Eric Seidel authored
* Remove stray PRODUCT_BUNDLE_IDENTIFIER This was erroneously added and overrides the bundle for the gallery causing signing to fail in my setup. @chinmaygarde * Remove PRODUCT_BUNDLE_IDENTIFIER from all Runner pbxproj's
-
Collin Jackson authored
-
- 15 Jul, 2016 1 commit
-
-
Adam Barth authored
Previously it wasn't included in the Runner target.
-
- 13 Jul, 2016 1 commit
-
-
Collin Jackson authored
-
- 12 Jul, 2016 1 commit
-
-
Collin Jackson authored
-
- 07 Jul, 2016 1 commit
-
-
Adam Barth authored
We want to use the FlutterViewController in this new project template. Fixes #4840
-
- 06 Jul, 2016 2 commits
-
-
Adam Barth authored
We now use a different approach for ios projects where the developer controls the Xcode project file. This patch removes the old ".generated" approach in favor of the new approach.
-
Adam Barth authored
This patch changes the default `flutter create` command to generate a HelloServices-style app on iOS. As a consequence, the Atom integration now fully works with HelloServices.
-