forked from flutter/plugins
-
Notifications
You must be signed in to change notification settings - Fork 0
update #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
update #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added 'settings' action
The platform is expecting NSURL where it got a string.
…it (#738) Document that retrieving dynamic link always return null after first attempt
…admob (#638) * Adds nonPersonalizedAds option to MobileAdTargetingInfo * Formats code * Bump version
…terView is being destroyed. (#739) Otherwise the exoplayer MediaPlayer objects continue generating frames after FlutterNativeView is destroyed and onFrameAvailableListener for the video target SurfaceTexture tries to access a missing engine instance. This is a workaround for widgets not receiving dispose signals when FlutterView is destroyed (flutter/flutter#19358). flutter/flutter#20989 tracks ensuring that resources are released.
* Remove a wrong assertion. Google play games service does not give us displayName. Closes flutter/flutter#19442
) This change adds a GoogleMap widget which shows a map as part of the widget tree. Each map uses a dedicated method channel named 'plugins.flutter.io/google_maps_$id', The Java GoogleMapsController class now extends PlatformView, and is the Java endpoint of the per map method channel. This change disables the plugin on iOS until we have an inlining solution for iOS.
This was a bit confusing, removing until the plugin supports iOS.
* Use api to allow support-v4 version resolution. If apps use image_picker and another plugin that uses a different version of support-v4 it should be visible to gradle to allow resolution to the latest version. * bump version
* Fix cloud functions podspec. This will fix compilation errors when doing a `pod install` because this package has static framework dependencies.
The focus of this CL is the overall widget/controller structure, and test plumbing. The API surface is just the bare minimum at this point (only loadUrl).
* Upload monitoring and management added for Android and iOS.
* listener on MobileAd shouldn't be final * Ad listeners shouldn't necessarily have to be set during Ad initialization. * add isLoaded method to firebase_admob MobileAd checking whether ad has been loaded.
…to Flutter (#672) * sending notification title and body to flutter * Safety checks for null pointer exceptions * Use remote data scheme on dart side
* Adding getWifiName to connectivity plugin
This is no longer used since #743, the empty list was just a left over.
* Added support for Firestore ArrayUnion, ArrayRemove and array-contains * Added FieldValue with support for delete and serverTimestamp values * Added Firestore.enablePersistence
The AndroidX migration didn't increment the major version for plugins >= 1.0.0. This commit reverts the code changes in the affected plugins. It's critical that the forward roll PR is published with this so that clients that have previously migrated aren't broken by the revert. I'm not planning on merging this into master until the forward roll (#1128) is also LGTMed and ready to merge. flutter/flutter#27128 flutter/flutter#23995
This PR forward rolls the earlier breaking changes with a proper semantic version upgrade. flutter/flutter#27128 flutter/flutter#23995
* android_alarm_manager background execution bug fixes * Updated android_alarm_manager to fix issues with "background start not allowed" when attempting to start AlarmService while backgrounded. * Switched to using a combination of BroadcastReceiver and JobIntentService from using a Service (launching a Service from an alarm Intent causes the "Background start not allowed" on Android 8+) * Alarm events received before the AlarmService isolate is finished initializing are now queued and processed once the isolate is initialized. * Updated CHANGELOG.md and README.md with new setup steps. * Bumped version to 0.4.0. Fixes #26846.
Fix for flutter/flutter#21709 Creating a second instance of the Connectivity object can cause the second instance overriding the first instance's stream channel. We can force the class to be a singleton because this class is designed to work as a singleton.
iOS implementation of the method channel API for adding and removing JavaScript channels. #1116 adds the Dart side support, the current PR will land first. flutter/flutter#24837
…ccession on Android (#1093)
Platform implementation of the method channel API for adding and removing JavaScript channels. #1116 adds the Dart side support, the current PR will land first. flutter/flutter#24837
Allows JavaScript code running in the WebView to send messages that will be received by the Flutter app's Dart code. To keep the PRs smaller this does not include the platform side implementations which will be sent in following PRs. Right now there are no return values on the JavaScript side, we could think of returning a JavaScript promise (or a promise equivalent) in the future, but as a first step I start without it (`evaluateJavascript` can be used to pass messages in the other direction so this shouldn't be a blocking limitation). I believe that if we end up adding a return value on the JavaScript side this could be done without making a breaking change. ### Sample usage Dart: ```dart WebView( javascriptChannels: <JavascriptChannel>[ JavascriptChannel(name: 'Print', onMessageReceived: (String msg) {print(msg); }), ].toSet(), ), ``` JavaScript (running inside the WebView): ```javascript Print.postMessage('Hello!'); ``` Fixes: flutter/flutter#24837
Added support for persisting alarms across reboots. Android doesn't automatically reschedule alarms after a reboot, so alarms set using this plugin would have to be scheduled manually after each reboot. With this change, alarms scheduled with the 'rescheduleOnReboot' flag set to true will be rescheduled at boot.
…#1157) A temporary workaround to fix the camera positioning issue mentioned in [flutter/flutter#24806](flutter/flutter#24806) A follow-up issue has been opened to track the 'real' fix.(flutter/flutter#27550)
#1135) Uses accelerometer data to determine device orientation when the photo is taken. Fixes flutter/flutter#26786 . flutter/flutter#26786
The app will still crash. Missing configuration is fatal. An app like this should never be released. A crash would be a good reminder for user to provide a proper fix before shipping the product. After this fix, a proper error message is shown to users.
This warning is only printed once per plugin on build failure. flutter/flutter#27106
* Fix biometrics check error below ios11.
Fixing [flutter/flutter#21972](flutter/flutter#21972) Android Alarm Manager will create a background flutter view to register plugins. When that happens, image_picker will be registered without an activity, which then caused crash. So we escape the registration process when there is no activity in the registrar.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.