2e78ed0ff9
## Description This introduces a list of packages that we will explicitly not pin. It is to be used for things where the package isn't actually published, but is a transitive dependency of another package included in the SDK. This happens with the `macros` package, for instance, which depends on the private, unpublished, `_macros` package where the SDK does some tricky things to depend on it (it depends on "any", but ships it as part of the SDK). Also ran `flutter update-packages --force-update` to update all of the pubspec files. ## Related Issues - Fixes #147656 ## Tests - Added a test that makes sure that explicitly unpinned packages don't show up in the pinned list. |
||
---|---|---|
.. | ||
android | ||
ios | ||
lib | ||
linux | ||
macos | ||
test_driver | ||
windows | ||
pubspec.yaml | ||
README.md |
Example of calling platform services from Flutter
This project demonstrates how to connect a Flutter app to platform-specific services.
You can read more about accessing platform and third-party services in Flutter.
iOS
You can use the commands flutter build
and flutter run
from the app's root
directory to build/run the app or you can open ios/Runner.xcworkspace
in Xcode
and build/run the project as usual.
Android
You can use the commands flutter build
and flutter run
from the app's root
directory to build/run the app or to build with Android Studio, open the
android
folder in Android Studio and build the project as usual.
Windows
You can use the commands flutter build
and flutter run
from the app's root
directory to build/run the app or you can build once then open
build\windows\platform_channel.sln
in Visual Studio to build and run.