flutter#2822)

* Stable null safety release camera_platform_interface

* Update minimum plugin_platform_interface version

* Update version of cross_file to 0.3.1

Migrates the app-facing package to null safety. Includes replacing Mockito with a custom fake/mock.

Fixes an issue where the example didn't handle dialogs being canceled, which was highlighted by the NNBD migration. (Previously, they would cause null assertions at runtime, which wasn't noticed during development. NNBD for the win!)

Fixes flutter/flutter#75235

`io.flutter.embedded_views_preview` is not required since version `1.0.0`, so doesn't need to be in the example.

The action won't work on the simulator works on physical iOS device which was not mentioned here so it was added

Co-authored-by: Michael Klimushyn <[email protected]>
Co-authored-by: Stuart Morgan <[email protected]>

…lutter#3642)

Migrates to NNBD.
Replaces Mockito-based fakes with test's Fake.

… leading dots. (flutter#3451)

…nel is called. (flutter#3639)

To avoid intra-repo plugin conflicts during the NNBD stable migration,
`plugin_platform_interface` allowed either 1.x or 2.0. However, 1.0.x
isn't null-safe so this can cause apps that don't have all their
packages fully updated can fail to run in strong mode (due to having an
old local `plugin_platform_interface`.

Now that everything has been updated, we can bump all the minimums so
that people updating their plugins will get new versions of the
dependency.

Stable NNBD release for the camera package.

With this PR I also migrated the example App to sound null safe.

Replaces the problematic Mockito mock with a manual mock that handles
null and non-null types correctly.

Removes the unit test of the example app, since it's not adding any
actual coverage.

Removes the opt-out now that the underlying issue is fixed

…utter#3664)

…er#3663)

…lutter#3662)

…st plugins (flutter#3673)

Co-authored-by: David Iglesias Teixeira <[email protected]>

…#3675)

This PR moves the integration tests of this package to conform with the latest best practices for web plugins.

Includes cleanup to simplify our setup. Major changes:
- Eliminate the NNBD plugin filtering for stable.
- Remove the temporarily-added beta branch testing.
- Enable Linux, macOS, and web on stable (Windows is LUCI-based)
- Combine the two different macOS matrix configurations now that they
  are the same.
- Combine the two different Linux matrix configurations by using a single
  Dockerfile (which now also includes clang-format)
  - The web integration smoke test temporarily still uses the old Dockerfile,
    now renamed, because the driver installer script doesn't support
    Chrome 89 yet.
- Move most of the Linux tasks to lower-CPU machines to allow more
  tasks to run in parallel without hitting the community limit.
- Reorder the tasks slightly and give them comments to identify
  platform groupings
- Enabled web "build all plugins together" and "build all examples"
  tests

…3679)

…ety integration tests. (flutter#3681)

…rametrized `clientId` (flutter#3686)

…3689)

Replaces deprecated import with current version.

The package now lives in flutter/packages.

…ences on Android (flutter#3684)

Uses an actual queue, rather than a one-element handoff "queue", for the single-thread background processing of commits.

…lity (flutter#3685)

…lutter#3668)

This makes a few improvements to CI throughput:
- Moves the flutter channel+upgrade step into each step, rather then doing it for both channels in the setup step. This avoids pointlessly doing twice the work in every setup (downloading two channels, only one of which will be used)
- Re-enables credits for macOS tasks. These were disabled in a recent chance since I was unifying configurations, but it turns out that without credits there is *no* parallelization of macOS tasks, which makes the end-to-end time very long.
- Dials back the Linux VM requirements based on looking at the new CPU and memory usage graphs for runs:
  - No task was ever reaching 4 CPUs or 12 GB of memory, so use those values for heavy workload; this will double concurrency of the heavy-workload tasks and should have no impact on run length.
  - Linux build+drive was extremely low usage, so move it to the light workload group.

…ANGELOG and pubspec matches. (flutter#3678)

The package now lives in flutter/packages.

Signed-off-by: Sunbreak <[email protected]>

Signed-off-by: Sunbreak <[email protected]>

...so that they are listed in more or less the likely order that people will do them in.

As recommended in flutter/website#5466

Adds a new CI check that all code files have a copyright+license block (and that it's one we are expecting to see).

Fixes the ~350 files (!) that did not have them. This includes all of the files in the .../example/ directories, following the example of flutter/flutter. (This does mean some manual intervention will be needed when generating new example directories in the future, but it's one-time per example.)

Also standardized some variants that used different line breaks than most of the rest of the repo (likely added since I standardized them all a while ago, but didn't add a check for at the time to enforce going forward), to simplify the checks.

Fixes flutter/flutter#77114

…or ids (flutter#3718)

Renames the old analysis_options.yaml to analysis_options_legacy.yaml,
replacing it with a slightly modified copy of flutter/flutter's analysis
options.

Each plugins has a temporary local analysis_options.yaml that points to
the legacy version. This allows for inceremental conversion on a
per-plugin basis, which should make the problem more tractable.

Since this hasn't yet been enabled for any packages, it's likely that as
it is we'll find a few local modification we need to make to the root
analysis_options (e.g., things that conflict with 'dart format').

Part of flutter/flutter#76229

…ter#3640)

This ensures that the AUTHORS list is distributed with the plugins whose copyright blocks refer to the project authors, for ease of reference. This is currently a copy of the top-level authors list, but over time they are expected to diverge as people contribute to specific plugins.

This does not bump plugin versions or CHANGLELOGs, since it has no effect on the plugin itself; it will be picked up over time as we ship new versions of plugins.

Part of flutter/flutter#78448

- Replaces "the Flutter project authors" with the repo-standard version "The Flutter Authors"
  - Updates the license check not to allow "the Flutter project authors" in the future
- Fixes a few minor cosmetic variations that had crept back into LICENSE files since my
  mass-standardization of those files.
  - Updates the license check to validate those to prevent such drift in the future.

In all copyright messages (and in the Xcode project organization name) standardize on "The Flutter Authors", adding "The Chromium Authors" to the Flutter AUTHORS list. This reduces inconsistency in the copyright lines in this repository, moving closer to a single consistent copyright+license (as in flutter/engine and flutter/flutter)

Updates the validation script to no longer accept "The Chromium Authors" or "the Chromium project authors" in first-party code.

…ter#3723)

Updates integration_test README to note that the published version is deprecated and direct people to the SDK version.
Updates all plugins here to use the SDK version.

Standardizes all first-party copyrights on a single year, as is done in flutter/flutter and flutter/engine. All code now uses 2013, which is the earliest year that was in any existing copyright notice.

The script checks now enforce the exact format of first-party licenses and copyrights.

Fixes flutter/flutter#78448

This change enables the integration_tests of the following packages to run in Cirrus CI:

* google_sign_in_web
* connectivity_for_web
* google_maps_flutter_web
* url_launcher_web

…er#3735)

* Moved quickactions to a subfolder

* Added platform interface with tests

* Added exports

* Formatted, made initialize return Future<void> instead of void

* Fixed formatting

* formatting

* Fixed analyze issue with import

* Fixed formatting

* Fixed formatting

* Added license in files

* Removed accidental \\\

* changed license to Flutter 2017

* Moved quickactions to a subfolder

* Added platform interface with tests

* Added exports

* Formatted, made initialize return Future<void> instead of void

* Fixed formatting

* formatting

* Fixed analyze issue with import

* Fixed formatting

* Fixed formatting

* Added license in files

* Removed accidental \\\

* changed license to Flutter 2017

* Implemented feedback

* Changed 2017 to 2013

* Changed 2017 to 2013

* Implemented feedback.

* Use flutter gcp project for linux tasks.

Bug: flutter/flutter#77624

* Merge upstream changes and change cluster.

* Add test_script back.

* Fix iOS rotation issue

* Fix orientation issues on iOS

* Merged with master and added test

* Test RotationBox turns according to device orientation

* Fix formatting

* Removed merge conflict tags from CHANGELOG

* Fix license header in test

platform_interface portion of flutter#3671

…er#3742)

…r#3748)

* Add CUSTOM_ANALYSIS_PLUGINS back with all the plugins that now have a custom analysis_options.yaml

This reverts commit a303d6d.

…n types (flutter#3754)

During the null-safety migration I accepted the auto-migrator use of as Future<T> to handle invokeMethod<T> returning a T?. I didn't realize that as does not actually do that kind of casting, and will fail with "type 'Future<T?>' is not a subtype of type 'Future<T>' in type cast".

There were no tests that exercised these methods in any way, so automated tests didn't catch the bug. This adds a minimal test that calls all of the non-void methods to ensure that they don't explode (and a TODO to backfill full unit tests of the entire method channel).

Fixes flutter/flutter#78426
Fixes flutter/flutter#78856

Fixes an obsolete link.

This enables to pass HTTP headers to VideoPlayerController.network.

Fixes: flutter/flutter#16466

Fixes flutter/flutter#79089