graphql.servlet.asyncModeEnabled is removed from GraphQLServletProperties.java after 8.0.0 version. How to disable this with 11.0.0?
I have raised a bug with graphql and they are introducing the property again with v11.1.0
https://github.com/graphql-java-kickstart/graphql-spring-boot/discussions/539
Related
I'm receiving the following error while using Firebase analytics (6.3.0):
Note: C:\src\flutter\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_analytics-6.3.0\android\src\main\java\io\flutter\plugins\firebaseanalytics\FirebaseAnalyticsPlugin.java uses or overrides a deprecated API.
Downgrade to version firebase analytics 6.2 to resolve the issue temporarily.
firebase_analytics: ^6.2.0
Upgrade your analytics version:smile:
firebase_analytics: ^9.3.4
I am trying to access the local database on the device while the app is completely closed, to achieve this I am using the sqlite plugin sqflite: ^1.2.0 and the background fetch plugin background_fetch: ^0.4.0.
I am able to register the headless background task with no issues, its when I try to run the background tasks, I get the following error!
The plugins seems to work fine while the app is running, or put into background mode.
Any suggestions please?
Error
[ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: MissingPluginException(No implementation found for method getDatabasesPath on channel com.tekartik.sqflite)
Flutter version:
Flutter 1.12.13+hotfix.7 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 9f5ff2306b (11 days ago) • 2020-01-26 22:38:26 -0800
Engine • revision a67792536c
Tools • Dart 2.7.0
Flutter Doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.7, on Mac OS X 10.15.2 19C57, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.5)
[✓] Connected device (1 available)
• No issues found!
You can try looking at sqflite troubleshooting section on their Github page, especially the one related to your error. Let me paste the bits from that page here.
This error is typically a build/setup error after adding the dependency.
Try all the steps defined at the top of the documents
Make sure you stop the current running application if any
Force a flutter packages get
Try to clean your build folder flutter clean
On iOS, you can try to force a pod install / pod update
Search for other bugs in flutter like this, other people face the same issue with other plugins so it is likely not sqflite related
Advanced checks:
Check the GeneratedPluginRegistrant file that flutter run should have generated in your project contains a line registering the plugin.
Android:
SqflitePlugin.registerWith(registry.registrarFor("com.tekartik.sqflite.SqflitePlugin"));
iOS:
[SqflitePlugin registerWithRegistrar:[registry registrarForPlugin:#"SqflitePlugin"]];
Check MainActivity.java (Android) contains a call to GeneratedPluginRegistrant asking it to register itself. This call should be made from the app launch method (onCreate).
public class MainActivity extends FlutterActivity {
#Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
GeneratedPluginRegistrant.registerWith(this);
}
}
Check AppDelegate.m (iOS) contains a call to GeneratedPluginRegistrant asking it to register itself. This call should be made from the app launch method (application:didFinishLaunchingWithOptions:).
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
[GeneratedPluginRegistrant registerWithRegistry:self];
return [super application:application didFinishLaunchingWithOptions:launchOptions];
}
Before raising this issue, try adding another well established plugin (the simplest being path_provider or shared_preferences) to see if you get the error here as well.
There has been some experiments about using sqflite from a background isolate and I'm not sure about the plugin support here. Anyway the transaction mechanism is not safe across isolate in the same process so I advise using sqflite from the main isolate (it already uses its own thread).
If your case is the same as mine, I have a custom plugin with Kotlin, so I didn't import GeneratedPluginRegistrant.registerWith(this) at the MainActivity. Instead, I implemented it at the start of the configureFlutterEngine() function and it worked perfectly.
import io.flutter.plugins.GeneratedPluginRegistrant
class MainActivity : FlutterActivity() {
private val CHANNEL = "getEpubs"
var _eventSink: EventChannel.EventSink? = null
override fun configureFlutterEngine(#NonNull flutterEngine: FlutterEngine) {
GeneratedPluginRegistrant.registerWith(flutterEngine)
}
This registers the generated sqflite plugin access to the database on the device.
(Sorry for the Kotlin code, but you can change it to Java.)
Don't forget to import:
io.flutter.plugins.GeneratedPluginRegistrant
This may be because one of the other plugins in your project is failing during plugin registration and preventing other plugins listed below it from being registered.
If you see the line below in your logs,
Tried to automatically register plugins with FlutterEngine #{engine hash appears here} but could not find and invoke the GeneratedPluginRegistrant;
set a break point in GeneratedPluginRegister's registerGeneratedPlugins() static method to see what exception is being thrown.
In my case I was using a plugin that called io.flutter.plugin.common.PluginRegistry.Registrar's activity() method which returns null when there is no foreground activity in the application.
My ionic app can't running on android devices and i get this error :
'Cordova Play Services Version Adapter' has detected an error. The following dependencies of 'Google Play Services' are not compatible: You have an incompatibility of versions with the following dependencies of 'Google Play Services':
- 'com.google.android.gms:play-services-base:11.0.4'
- 'com.google.android.gms:play-services-tagmanager:+'
- 'com.google.firebase:firebase-core:+'
- 'com.google.firebase:firebase-messaging:+'
- 'com.google.firebase:firebase-config:+'
- 'com.google.firebase:firebase-perf:+'
It doesn't exists a version of 'Google Play Services' that includes all these dependencies.
All dependencies of 'Google Play Services' must have the same version.
The application may not compile."
thanks.
Try to find the file platforms/android/project.properties and update the lines
cordova.system.library.12=com.google.android.gms:play-services-auth:11.0.4
cordova.system.library.13=com.google.android.gms:play-services-identity:11.0.4
to
cordova.system.library.12=com.google.android.gms:play-services-auth:+
cordova.system.library.13=com.google.android.gms:play-services-identity:+
Selast has suggest a good manual solution for resolving this.
An alternative is to use a plugin which will automatically override the play services version so that everyone asks for the same version.
This plugin will provide that functionality:
appfeel/cordova-play-services-version-adapter: Cordova/Ionic Google Play Services Versions Incompatibility Adapter
To use it just type this into the console:
ionic cordova plugin add cordova-play-services-version-adapter
I was using FirebaseDynamicLinks in my Xamarin forms project (everything works fine) and I decided to update my nuget packages.. but after I update Xamarin.Firebase.DynamicLinks (and all dependencies) I got null after calling FirebaseDynamicLinks.Instance.
There was some major changes? Do I need to modify my code somehow after this update? Thanks for any help!
I found this in logs, so my google-services.json should be right, right?
FirebaseInitProvider: FirebaseApp initialization successful
Xamarin.Android SDK Version: 9.3.0.23
Operating System & Version: Win 10, 1803
So if not necessary now, suggest downgrading to previous version of Xamarin.Firebase.DynamicLinks. Maybe there are something not incompatible or new methods not be used correctly.
Dart recently added a support for async/await keywords:
https://www.dartlang.org/articles/await-async/
I tried to run a simple code but Chrome Dev Editor does not recognise async keyword
import 'dart:async';
void main() async {
}
Am I doing something wrong (something to modify in the pubspec.yaml ?) or is it just that this feature is not supported yet on Chrome Dev Editor ?
Edit:
Ok, so for know it seem that async/await seems to be more an experimental feature:
https://www.dartlang.org/docs/dart-up-and-running/ch02.html#async-opt-in
To opt into asynchrony support in Dart Editor, go to Preferences, click Experimental, and select Enable Async Support.
In dart and dartanalyzer, use the --enable-async command-line flag:
dart --enable-async async_await.dart
dartanalyzer --enable-async async_await.dart
Unfortunatly, it seems only to work for Dart Editor, not CDE.
Also, dart does not currently support the conversion into javascript without adding a package:
dependencies:
async_await:
git: https://github.com/dart-lang/async_await.git
transformers:
- async_await
So currently it's not supported.
Now there is an issue on this problem: https://github.com/dart-lang/chromedeveditor/issues/3822
Thank you for all your answer
Wait & see...
Did you import the async module?
From the page you linked:
The features described in this article are still under development. Not all the parts of the system necessarily comply with the spec. Early adopters may need to import dart:async for these features to work. Ultimately, Future should move to dart:core and be universally available.
I'm on my Chromebook right now (and can't verify), but I believe you have to enable it under experimental features in the settings.
I don't know whether this helps with CDE, but the Asynchrony part of the Dart language tour has some information on opting in to asynchrony support for other tools.