文件最后提交记录最后更新时间
Ensure Example Packages Work on Android API 36 (#9241) Ensured the example plugin apps on Android work on Android API 36 by updating configurations and sucessfully running flutter build apk (means the app can successfully build + all dependencies are resolvable). For compatibility with Android API 36, the example plugin apps on Android should have the following configurations: targetSdk: 36 compileSdk: 36 AGP version: 8.9.1 Gradle version: 8.11.1 Most packages no longer require a manual bump of targetSdk and compileSdk due to usage of values from Flutter Gradle Plugin. Below is a list of example plugin apps on Android: Partially Adresses https://github.com/flutter/flutter/issues/163071 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.1 年前
[video_player] Federate mobile implementations (#4712) Moves the iOS and Android implementations to their own federated packages. The iOS implementation package uses the name avfoundation rather than ios since it is likely that a macOS implementation could share a significant amount of code. As part of the federation, migrates the mobile implementations to using in-package method channels rather than the shared method channel. Currently these are just duplicates of the existing method channels; updating them to new version of Pigeon will be done in a separate PR later. Temporarily marks video_player as unpublishable to allow the implementations to be moved, rather than copied and deleted, in order to better preserve git history. A follow-up PR will restore it to publishable form. No version change: The changes to video_player_platform_interface only affect development of the plugin, not use of the plugin. Part of https://github.com/flutter/flutter/issues/68498 Part of https://github.com/flutter/flutter/issues/942244 年前
[camera,video_player] Update Android to 3.29 minimum (#9317) This is a prequel to https://github.com/flutter/packages/pull/9316 to separate out auto-generated changes. All this does is: - Set the minimum SDK version to 3.29. - Run the autoformatter—which changes a ton of things because the 3.29 minimum opts into the new formatter. ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.11 个月前
[camera,video_player] Update Android to 3.29 minimum (#9317) This is a prequel to https://github.com/flutter/packages/pull/9316 to separate out auto-generated changes. All this does is: - Set the minimum SDK version to 3.29. - Run the autoformatter—which changes a ton of things because the 3.29 minimum opts into the new formatter. ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.11 个月前
[various] Remove unused flutter_driver dependencies (#4347) flutter_driver has been mostly replaced by integration_test, but we still have a lot of remaining dependencies on the package. This removes the dependency from pubspec.yaml for all plugins that aren't actually importing it. It also removes an old video_player test that has been disabled for years that was never updated from flutter_driver to integration_test; we've since added a lot more testing to video_player, so in practice this is cruft that we can just remove. Closes https://github.com/flutter/flutter/issues/852242 年前
[video_player] Federate mobile implementations (#4712) Moves the iOS and Android implementations to their own federated packages. The iOS implementation package uses the name avfoundation rather than ios since it is likely that a macOS implementation could share a significant amount of code. As part of the federation, migrates the mobile implementations to using in-package method channels rather than the shared method channel. Currently these are just duplicates of the existing method channels; updating them to new version of Pigeon will be done in a separate PR later. Temporarily marks video_player as unpublishable to allow the implementations to be moved, rather than copied and deleted, in order to better preserve git history. A follow-up PR will restore it to publishable form. No version change: The changes to video_player_platform_interface only affect development of the plugin, not use of the plugin. Part of https://github.com/flutter/flutter/issues/68498 Part of https://github.com/flutter/flutter/issues/942244 年前
[various] Speed up build-examples (#3849) https://github.com/flutter/flutter/issues/125707 - Create pluginTools config for every example that shrunk material icons and had an android config Likely some build caching but before/after If someone knows how to clean the cache or force a rebuild I will give more accurate after numbers. Command time dart run ./script/tool/bin/flutter_plugin_tools.dart build-examples --apk Secondary validation from @stuartmorgan who discovered this is between a 10% and 25% speed increase. Existing tests add confidence this is non-breaking. New tests not required because these are optional flags. Validation this does not change is low consequence. Test update to exclude these config files from changelog requirements.3 年前
[tools] Require implementation package README warning (#6459) 3 年前
[camera,video_player] Update Android to 3.29 minimum (#9317) This is a prequel to https://github.com/flutter/packages/pull/9316 to separate out auto-generated changes. All this does is: - Set the minimum SDK version to 3.29. - Run the autoformatter—which changes a ton of things because the 3.29 minimum opts into the new formatter. ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.11 个月前
README.md

Platform Implementation Test App

This is a test app for manual testing and automated integration testing of this platform implementation. It is not intended to demonstrate actual use of this package, since the intent is that plugin clients use the app-facing package.

Unless you are making changes to this implementation package, this example is very unlikely to be relevant.