Cannot execute operation because FlutterJNI is not attached to native.

App crashes and exception
Cannot execute operation because FlutterJNI is not attached to native.

appears if I close application during await getCurrentPosition in geolocator plugin ^3.0.0.(Android).
It have started after newest flutter upgrade. Not geolocator upgrade !
Log
E/AndroidRuntime( 4949): FATAL EXCEPTION: main
E/AndroidRuntime( 4949): Process: ru.ser.spm, PID: 4949
E/AndroidRuntime( 4949): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
E/AndroidRuntime( 4949): at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:523)
E/AndroidRuntime( 4949): at io.flutter.embedding.engine.FlutterJNI.invokePlatformMessageResponseCallback(FlutterJNI.java:486)
E/AndroidRuntime( 4949): at io.flutter.embedding.engine.dart.DartMessenger$Reply.reply(DartMessenger.java:129)
E/AndroidRuntime( 4949): at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.success(MethodChannel.java:204)
E/AndroidRuntime( 4949): at com.baseflow.flutter.plugin.geolocator.data.Result.success(Result.java:22)
E/AndroidRuntime( 4949): at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask.reportLocationUpdate(LocationUpdatesUsingLocationServicesTask.java:108)
E/AndroidRuntime( 4949): at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask.access$000(LocationUpdatesUsingLocationServicesTask.java:19)
E/AndroidRuntime( 4949): at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask$1.onLocationResult(LocationUpdatesUsingLocationServicesTask.java:40)
E/AndroidRuntime( 4949): at com.google.android.gms.internal.location.zzau.notifyListener(Unknown Source:4)
E/AndroidRuntime( 4949): at com.google.android.gms.common.api.internal.ListenerHolder.notifyListenerInternal(Unknown Source:17)
E/AndroidRuntime( 4949): at com.google.android.gms.common.api.internal.ListenerHolder$zaa.handleMessage(Unknown Source:5)
E/AndroidRuntime( 4949): at android.os.Handler.dispatchMessage(Handler.java:105)
E/AndroidRuntime( 4949): at android.os.Looper.loop(Looper.java:164)
E/AndroidRuntime( 4949): at android.app.ActivityThread.main(ActivityThread.java:6944)
E/AndroidRuntime( 4949): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4949): at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
E/AndroidRuntime( 4949): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Lost connection to device.

Configuration
geolocator ^3.0.0

[✓] Flutter (Channel dev, v1.2.2, on Mac OS X 10.14.3 18D109, locale ru-RU)
• Flutter version 1.2.2 at /Users/pavelmiheev/Flutter
• Framework revision 007a415c2a (5 days ago), 2019-02-21 20:22:47 -0800
• Engine revision f1f19bba8f
• Dart version 2.2.0 (build 2.2.0-dev.2.1 c92d5ca288)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /Users/pavelmiheev/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
• All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 10.1, Build version 10B61
• ios-deploy 2.0.0
• CocoaPods version 1.5.3

[✓] Android Studio (version 3.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 33.3.1
• Dart plugin version 182.5215
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] Connected device (1 available)
• SM G930F • ad0b1603812a66dbad • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

Additionally. Geolocator had nothing to do.
This happens if you quickly exit the application during launching
FATAL EXCEPTION: main
E/AndroidRuntime(23688): Process: ru.serp.spm, PID: 23688
E/AndroidRuntime(23688): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
E/AndroidRuntime(23688): 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:514)
E/AndroidRuntime(23688): 	at io.flutter.embedding.engine.FlutterJNI.invokePlatformMessageResponseCallback(FlutterJNI.java:477)
E/AndroidRuntime(23688): 	at io.flutter.embedding.engine.dart.DartMessenger$Reply.reply(DartMessenger.java:129)
E/AndroidRuntime(23688): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.success(MethodChannel.java:204)
E/AndroidRuntime(23688): 	at com.tekartik.sqflite.SqflitePlugin$BgResult$1.run(SqflitePlugin.java:88)
E/AndroidRuntime(23688): 	at android.os.Handler.handleCallback(Handler.java:873)
E/AndroidRuntime(23688): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(23688): 	at android.os.Looper.loop(Looper.java:193)
E/AndroidRuntime(23688): 	at android.app.ActivityThread.main(ActivityThread.java:6669)
E/AndroidRuntime(23688): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(23688): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/AndroidRuntime(23688): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
I/Process (23688): Sending signal. PID: 23688 SIG: 9
Lost connection to device.

I'm having similar issues with:
• Flutter version 1.3.0 at /Users/luigi/dev/app/flutter-alpha-20171102
• Framework revision 3054a93579 (3 days ago), 2019-02-27 14:49:49 -0800
• Engine revision 4434a39c7d
• Dart version 2.2.0 (build 2.2.0-dev.2.1 0f9a5198bd)

I am facing the same issue without geolocator.
I am using Location
Flutter version 1.3.0

Problem seems to have started after Roll engine f7306394e303..1d0615af4ee5

Same happens with 5. at io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$9.onSuccess (Unknown Source:8) (previous four functions in the stack are the same) on Xiaomi Mi A2 (jasmine_sprout), Android 9.

D/SurfaceView(19441): surfaceDestroyed 1 io.flutter.view.FlutterView{9cd6c0b VFE...... .F....I. 0,0-1080,1920}
D/AndroidRuntime(19441): Shutting down VM
E/AndroidRuntime(19441): FATAL EXCEPTION: main
E/AndroidRuntime(19441): Process: ru.serviopump.spmobile, PID: 19441
E/AndroidRuntime(19441): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
E/AndroidRuntime(19441): 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:514)
E/AndroidRuntime(19441): 	at io.flutter.embedding.engine.FlutterJNI.dispatchPlatformMessage(FlutterJNI.java:444)
E/AndroidRuntime(19441): 	at io.flutter.embedding.engine.dart.DartMessenger.send(DartMessenger.java:74)
E/AndroidRuntime(19441): 	at io.flutter.embedding.engine.dart.DartExecutor.send(DartExecutor.java:163)
E/AndroidRuntime(19441): 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:84)
E/AndroidRuntime(19441): 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:71)
E/AndroidRuntime(19441): 	at io.flutter.embedding.engine.systemchannels.TextInputChannel.updateEditingState(TextInputChannel.java:117)
E/AndroidRuntime(19441): 	at io.flutter.plugin.editing.InputConnectionAdaptor.updateEditingState(InputConnectionAdaptor.java:61)
E/AndroidRuntime(19441): 	at io.flutter.plugin.editing.InputConnectionAdaptor.endBatchEdit(InputConnectionAdaptor.java:86)
E/AndroidRuntime(19441): 	at android.view.inputmethod.BaseInputConnection.finishComposingText(BaseInputConnection.java:444)
E/AndroidRuntime(19441): 	at android.view.inputmethod.BaseInputConnection.closeConnection(BaseInputConnection.java:163)
E/AndroidRuntime(19441): 	at com.android.internal.view.IInputConnectionWrapper.executeMessage(IInputConnectionWrapper.java:541)
E/AndroidRuntime(19441): 	at com.android.internal.view.IInputConnectionWrapper.dispatchMessage(IInputConnectionWrapper.java:225)
E/AndroidRuntime(19441): 	at com.android.internal.view.IInputConnectionWrapper.closeConnection(IInputConnectionWrapper.java:211)
E/AndroidRuntime(19441): 	at android.view.inputmethod.InputMethodManager$ControlledInputConnectionWrapper.deactivate(InputMethodManager.java:644)
E/AndroidRuntime(19441): 	at android.view.inputmethod.InputMethodManager.clearConnectionLocked(InputMethodManager.java:1016)
E/AndroidRuntime(19441): 	at android.view.inputmethod.InputMethodManager.finishInputLocked(InputMethodManager.java:1038)
E/AndroidRuntime(19441): 	at android.view.inputmethod.InputMethodManager.windowDismissed(InputMethodManager.java:1838)
E/AndroidRuntime(19441): 	at android.view.WindowManagerGlobal.removeViewLocked(WindowManagerGlobal.java:494)
E/AndroidRuntime(19441): 	at android.view.WindowManagerGlobal.removeView(WindowManagerGlobal.java:435)
E/AndroidRuntime(19441): 	at android.view.WindowManagerImpl.removeViewImmediate(WindowManagerImpl.java:131)
E/AndroidRuntime(19441): 	at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4645)
E/AndroidRuntime(19441): 	at android.app.ActivityThread.-wrap5(Unknown Source:0)
E/AndroidRuntime(19441): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1757)
E/AndroidRuntime(19441): 	at android.os.Handler.dispatchMessage(Handler.java:105)
E/AndroidRuntime(19441): 	at android.os.Looper.loop(Looper.java:164)
E/AndroidRuntime(19441): 	at android.app.ActivityThread.main(ActivityThread.java:6944)
E/AndroidRuntime(19441): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(19441): 	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
E/AndroidRuntime(19441): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Lost connection to device.

App crashes while closing it, I'm not even using geolocator plugin, the error log is same but have some log related to cloud firestore.

I have similar issue when using connectivity plugin https://pub.dartlang.org/packages/connectivity#-readme-tab-
App crashes when I close the app(by pressing back button) and then run it again and turn on/off internet conneciton.

Those of you (@arteki65, @MDSADABWASIM, @AresVampire and others) who are facing this issue but hasn't upvoted it yet, I request you to please do so, so that Flutter team can put this issue on priority.
Thanks

Also having this issue

@Theunodb Please read last message of this thread again and upvote this issue.

@zoechi Any suggestions.

I'm just not able to push my app on the Play store because of this issue. Hoping to get a quick fix. Thanks @zoechi for putting it in goals.

Seems like these two methods get called before crash From
engine/shell/platform/android/io/flutter/embedding/engine/FlutterJNI.java class
`private void ensureNotAttachedToNative() {
if (nativePlatformViewId != null) {
throw new RuntimeException("Cannot execute operation because FlutterJNI is attached to native.");
}
}
private void ensureAttachedToNative() {
if (nativePlatformViewId == null) {
throw new RuntimeException("Cannot execute operation because FlutterJNI is not attached to native.");
}
}`

cc @matthew-carroll

I'll look into this tomorrow.  For now, switching from an exception to a log warning should fix this issue.
@jason-simmons @mklim do you have thoughts on what the appropriate action is in the scenario where a platform message comes through after the FlutterView has been destroyed?  In some cases a no-op might be fine, but in other cases this might signal an important missed message, depending on the plugin in question.

This bug should be fixed here: https://github.com/flutter/engine/pull/8170

I'm on dev channel and changes made are in the master channel (which it how it works) but is there any way to edit this file manually in the dev channel?
I tried searching for the file but all I get is FlutterJNI.class (compiled file), I can't get the source code. So, can I make these changes on my own without having to update flutter.
Thanks to all developers who are striving to fix issues real quick. 💯

I'm on dev channel too. Our fate is hoping for a quick dev release )

@dark-chocolate you could choose to compile with a custom version of the engine.  To do that, you would follow the standard instructions for working on the engine, available in the Wiki.  However, if you're not already setup to do that then you are probably better off just waiting for the downstream roll.

Updated to 1.3.11. The problem is not resolved
[✓] Flutter (Channel dev, v1.3.11, on Mac OS X 10.14.3 18D109, locale ru-RU)
• Flutter version 1.3.11 at /Users/pavelmiheev/Flutter
• Framework revision 73fb457cae (3 days ago), 2019-03-14 23:51:18 -0700
• Engine revision 403337ebb8
• Dart version 2.2.1 (build 2.2.1-dev.1.0 None)
java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
E/AndroidRuntime(  704): 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:532)
E/AndroidRuntime(  704): 	at io.flutter.embedding.engine.FlutterJNI.invokePlatformMessageResponseCallback(FlutterJNI.java:495)
E/AndroidRuntime(  704): 	at io.flutter.embedding.engine.dart.DartMessenger$Reply.reply(DartMessenger.java:129)
E/AndroidRuntime(  704): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.success(MethodChannel.java:204)
E/AndroidRuntime(  704): 	at com.tekartik.sqflite.SqflitePlugin$BgResult$1.run(SqflitePlugin.java:91)
E/AndroidRuntime(  704): 	at android.os.Handler.handleCallback(Handler.java:873)
E/AndroidRuntime(  704): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(  704): 	at android.os.Looper.loop(Looper.java:214)
E/AndroidRuntime(  704): 	at android.app.ActivityThread.main(ActivityThread.java:7032)
E/AndroidRuntime(  704): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(  704): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/AndroidRuntime(  704): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)

@jonahwilliams I think the issue is resolved, it must just be taking a while to get the roll through.  Notice that the line numbers in the latest callstack don't match FlutterJNI, and notice that the ensureAttachedToNative is no longer even called in FlutterJNI from invokePlatformMessageResponseCallback:
https://github.com/flutter/engine/blob/master/shell/platform/android/io/flutter/embedding/engine/FlutterJNI.java
Should this ticket really be re-opened?

Error while updating to 1.3.13
error: Your local changes to the following files would be overwritten by merge:
examples/flutter_gallery/pubspec.yaml
packages/flutter_tools/pubspec.yaml
Please commit your changes or stash them before you merge.
Aborting
What is it ?

1.3.13. it seems the issue is solved. Thank you !

@pamir72 @matthew-carroll @zoechi
I've updated to 1.3.13 but still the issue persist. I am not sure why, there is also something interesting. When I run flutter doctor, here is the output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.3.13, on Mac OS X 10.14 18A389, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.3)
[✓] Connected device (1 available)

• No issues found!

And when I run flutter version here what it shows
...
v1.3.0
v1.3.1
v1.3.10
v1.3.11
v1.3.12
v1.3.13
v1.3.2
v1.3.3
v1.3.4
v1.3.5
v1.3.6
v1.3.7
v1.3.8
v1.3.9

Am I doing something wrong?

@dark-chocolate can you please post your latest crash stacktrace?

@matthew-carroll Sure, here it is
  --------- beginning of crash
E: FATAL EXCEPTION: main
    Process: com.example.app, PID: 14078
    java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
        at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:553)
        at io.flutter.embedding.engine.FlutterJNI.dispatchPlatformMessage(FlutterJNI.java:477)
        at io.flutter.embedding.engine.dart.DartMessenger.send(DartMessenger.java:74)
        at io.flutter.embedding.engine.dart.DartExecutor.send(DartExecutor.java:149)
        at io.flutter.view.FlutterNativeView.send(FlutterNativeView.java:142)
        at io.flutter.plugin.common.EventChannel$IncomingStreamRequestHandler$EventSinkImplementation.success(EventChannel.java:213)
        at com.baseflow.flutter.plugin.geolocator.data.Result.success(Result.java:26)
        at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask.reportLocationUpdate(LocationUpdatesUsingLocationServicesTask.java:129)
        at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask.access$000(LocationUpdatesUsingLocationServicesTask.java:21)
        at com.baseflow.flutter.plugin.geolocator.tasks.LocationUpdatesUsingLocationServicesTask$1.onLocationResult(LocationUpdatesUsingLocationServicesTask.java:49)
        at com.google.android.gms.internal.location.zzau.notifyListener(Unknown Source:4)
        at com.google.android.gms.common.api.internal.ListenerHolder.notifyListenerInternal(Unknown Source:17)
        at com.google.android.gms.common.api.internal.ListenerHolder$zaa.handleMessage(Unknown Source:5)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:193)
        at android.app.ActivityThread.main(ActivityThread.java:6669)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
W:   Force finishing activity com.example.app/.MainActivity

Hmm...I use geolocator and I get warning in the log now. Not exception.

@pamir72 I'm also using the same (latest version of both flutter dev and geolocator) but I'm still having the issue. Hope @matthew-carroll comes up with a solution.

@pamir72 that warning is expected.  That will happen until we eventually determine the root cause.
@dark-chocolate somehow you're using a different version.  My guess is its because you're on the "dev" channel instead of the "master" channel.  You may have to wait longer for the update.  @pamir72 you said you were on the "master" channel, right?

@matthew-carroll pamir72 is also on dev channel just like me and his issue got solved in 1.3.13, below are the quotes from @pamir72

I'm on dev channel too. Our fate is hoping for a quick dev release )

1.3.13. it seems the issue is solved. Thank you !

@matthew-carroll I'm on dev

Other participants who also have upvoted this issue or having this issue and who are also running dev channel, please upgrade your flutter version by using flutter upgrade and let us know if that fixes your issue because it worked for pamir72 and failed for me including the fact that we both are using same dev channel, same package (geolocator).
Thank you :)

flutter doctor -v
[✓] Flutter (Channel dev, v1.3.13, on Mac OS X 10.13.6 17G65, locale zh-Hans-CN)
    • Flutter version 1.3.13 at /Users/shipuliu/Documents/flutter
    • Framework revision 59ce7d6bff (3 days ago), 2019-03-18 11:20:10 -0700
    • Engine revision e75f6de01f
    • Dart version 2.2.1 (build 2.2.1-dev.1.0 None)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/shipuliu/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio
      2.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

Log
03-21 11:27:54.649   998   998 I am_crash: [18017,0,com.tengyue360.student,15253060,java.lang.RuntimeException,Cannot execute operation because FlutterJNI is not attached to native.,FlutterJNI.java,553]
=========================================================================================================
03-21 11:30:20.519 22478 23151 I am_crash: [22930,0,com.tengyue360.student,13155908,java.lang.RuntimeException,Cannot execute operation because FlutterJNI is not attached to native.,FlutterJNI.java,553]
=========================================================================================================
03-21 11:27:54.459 18017 18017 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x417d1898)
=================================================================================================
03-21 11:27:54.649 18017 18017 E AndroidRuntime: FATAL EXCEPTION: main
03-21 11:27:54.649 18017 18017 E AndroidRuntime: java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:553)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.embedding.engine.FlutterJNI.dispatchPlatformMessage(FlutterJNI.java:477)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.embedding.engine.dart.DartMessenger.send(DartMessenger.java:74)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.embedding.engine.dart.DartExecutor.send(DartExecutor.java:163)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:84)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:71)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.embedding.engine.systemchannels.TextInputChannel.updateEditingState(TextInputChannel.java:117)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.plugin.editing.InputConnectionAdaptor.updateEditingState(InputConnectionAdaptor.java:61)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at io.flutter.plugin.editing.InputConnectionAdaptor.endBatchEdit(InputConnectionAdaptor.java:86)
03-21 11:27:54.649 18017 18017 E AndroidRuntime: 	at android.view.inputmethod.BaseInputConnection.finishComposingText(BaseInputConnection.java:272)
=================================================================================================
03-21 11:29:26.459 18017 18017 E AndroidRuntime: android.os.DeadObjectException
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at android.os.BinderProxy.transact(Native Method)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:3708)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:138)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at com.crashlytics.android.core.CrashlyticsUncaughtExceptionHandler.uncaughtException(CrashlyticsUncaughtExceptionHandler.java:51)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at android.support.v7.app.AppCompatDelegateImpl$1.uncaughtException(AppCompatDelegateImpl.java:143)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
03-21 11:29:26.459 18017 18017 E AndroidRuntime: 	at dalvik.system.NativeStart.main(Native Method)
=================================================================================================
03-21 11:30:18.249 22930 22930 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x417ad898)
=================================================================================================
03-21 11:30:20.519 22930 22930 E AndroidRuntime: FATAL EXCEPTION: main
03-21 11:30:20.519 22930 22930 E AndroidRuntime: java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:553)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.embedding.engine.FlutterJNI.dispatchPlatformMessage(FlutterJNI.java:477)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.embedding.engine.dart.DartMessenger.send(DartMessenger.java:74)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.embedding.engine.dart.DartExecutor.send(DartExecutor.java:163)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:84)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.plugin.common.MethodChannel.invokeMethod(MethodChannel.java:71)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.embedding.engine.systemchannels.TextInputChannel.updateEditingState(TextInputChannel.java:117)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.plugin.editing.InputConnectionAdaptor.updateEditingState(InputConnectionAdaptor.java:61)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at io.flutter.plugin.editing.InputConnectionAdaptor.endBatchEdit(InputConnectionAdaptor.java:86)
03-21 11:30:20.519 22930 22930 E AndroidRuntime: 	at android.view.inputmethod.BaseInputConnection.finishComposingText(BaseInputConnection.java:272)
=================================================================================================

This problem is very serious for me, which makes it impossible for me to publish the application. The pass rate is only 53.57%.

@dark-chocolate and @yy1300326388 can each of you try the master channel and see if your problem is solved on master?

I'm still seeing this error:
03-21 14:10:30.965 24510-24510/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.worldview.mobile, PID: 24510
    java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
        at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(Unknown Source)
        at io.flutter.embedding.engine.FlutterJNI.dispatchPlatformMessage(Unknown Source)
        at io.flutter.embedding.engine.dart.DartMessenger.send(Unknown Source)
        at io.flutter.embedding.engine.dart.DartExecutor.send(Unknown Source)
        at io.flutter.plugin.common.MethodChannel.invokeMethod(Unknown Source)
        at io.flutter.plugin.common.MethodChannel.invokeMethod(Unknown Source)
        at io.flutter.embedding.engine.systemchannels.TextInputChannel.updateEditingState(Unknown Source)
        at io.flutter.plugin.editing.InputConnectionAdaptor.updateEditingState(Unknown Source)
        at io.flutter.plugin.editing.InputConnectionAdaptor.endBatchEdit(Unknown Source)
        at android.view.inputmethod.BaseInputConnection.finishComposingText(BaseInputConnection.java:277)
        at android.view.inputmethod.InputMethodManager.reportFinishInputConnection(InputMethodManager.java:998)
        at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:4000)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:145)
        at android.app.ActivityThread.main(ActivityThread.java:6967)
        at java.lang.reflect.Method.invoke(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:372)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)

[✓] Flutter (Channel master, v1.3.14-pre.42, on Mac OS X 10.14.3 18D109, locale en-US)
    • Flutter version 1.3.14-pre.42 at /Users/jferguson/flutter
    • Framework revision db096cdfd8 (2 hours ago), 2019-03-21 10:32:43 -0700
    • Engine revision d4d4883216
    • Dart version 2.2.1 (build 2.2.1-dev.2.0 None)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/jferguson/Library/Android/sdk/
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/java
    • Java version Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.io/setup/#android-setup for detailed instructions.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio
    • Android Studio at /Applications/Android Studio 3.4 Preview.app/Contents
    • Flutter plugin version 33.2.2
    • Dart plugin version 183.5901
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b22)

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] Android Studio
    • Android Studio at /Applications/Android Studio 3.5 Preview.app/Contents
    • Flutter plugin version 33.4.2
    • Dart plugin version 183.5901
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Android Studio (version 3.3)
    • Android Studio at /Users/jferguson/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/182.5199772/Android Studio.app/Contents
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

@joshuaferguson are you seeing that error on the master channel?

Yes, this is currently on the master channel.

Ok, now I see where the confusion came from.  We're mixing up 2 different stacktraces in this ticket.  The one I originally fixed is not the one that has been referenced in the last few messages.
Here is a PR that should at least put an end to the crashes you are seeing:
https://github.com/flutter/engine/pull/8246
It is still unclear to me why the app is detaching from Flutter's C++ side and yet the app is still attempting to send platform messages.  I have filed another ticket to investigate the root cause:
https://github.com/flutter/flutter/issues/29757

AHHHH...I apologize for hijacking the thread!

No worries - they are related, and we need to get this fixed for you all.  Unfortunately, we'll need to go through another engine roll to get this fix out.  But I'll try to keep this thread updated.

@joshuaferguson @yy1300326388 @dark-chocolate Would you all mind providing your repro steps to cause this issue?  Was the app in foreground or background?  Were you interacting with it at the time of the issue?  Any other details that can help us repro on our end?

FYI - the latest PR for the bugfix just landed in the engine:
https://github.com/flutter/engine/pull/8246
Next we need to wait for an engine roll to bring this engine change into the Flutter framework on master.

@matthew-carroll I updated it to master and seems like the issue is solved (I mean there is no error but only warning),
W/FlutterJNI: Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: flutter.baseflow.com/geolocator/events. Response ID: 0

And if I close the app and opens it again, I keep getting this warning every second my app request a location update from geolocator, which I believe is not a good thing as far as performance is considered. I hope for a better fix.

@dark-chocolate when the following commit rolls into master, please try again and see if the problem is resolved.
https://github.com/flutter/engine/commit/68bd4f2c6479c19a4e4af6574db45900fcade346

is this bug fixed in beta or dev channel?

@nieben it is not fixed in either of them, I am on dev channel running v1.5.8, will have to wait more!

@nieben it is not fixed in either of them, I am on dev channel running v1.5.8, will have to wait more!

oh, thanks!

@matthew-carroll Problem still exsits. https://github.com/flutter/flutter/issues/33511 with flutter version 1.10.15

Problem still reproduce
Flutter 1.14.6 • channel dev • https://github.com/flutter/flutter.git
Framework • revision fabeb2a16f (8 days ago) • 2020-01-28 07:56:51 -0800
Engine • revision c4229bfbba
Tools • Dart 2.8.0 (build 2.8.0-dev.5.0 fc3af737c7)

Why this error comes

Why this Crash comes

Here same problem

Yep facing the same issue on Oneplus 5 running Android 9

I jsut started facing this issue now with Android 10. It started to happen because I migrated my project to Android V2 binding, but I have no idea how to workaround that.
Any idea?

We are using firebase_messaging_plugin.
FlutterJNI is properly attached for the first time when the app is opened or when the app is force stopped and opened.
But FlutterJNI is not attaching to the platform when the app is resumed after

The app is minimized using either back or home button/gesture
The app cleared from the recent apps tray

Background messages are received properly when the app goes to the background for the first time.
Due to this issue when the app goes to the background for the second time onwards background messages are not received.
I guess there is a problem is removing the FlutterJNI and reattaching it to the platform.

any fix for this?

Fatal Exception: java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:227)
at io.flutter.embedding.engine.FlutterJNI.setSemanticsEnabled(FlutterJNI.java:513)
at io.flutter.embedding.engine.systemchannels.AccessibilityChannel.onAndroidAccessibilityDisabled(AccessibilityChannel.java:110)
at io.flutter.view.AccessibilityBridge$2.onAccessibilityStateChanged(AccessibilityBridge.java:291)
at android.view.accessibility.AccessibilityManager.lambda$notifyAccessibilityStateChanged$0(AccessibilityManager.java:1157)
at android.view.accessibility.-$$Lambda$AccessibilityManager$yzw5NYY7_MfAQ9gLy3mVllchaXo.run(:4)
at android.os.Handler.handleCallback(Handler.java:907)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)

I'm also facing this issue while using flutter webview plugin

[android] on "app exit" : Runtime exception at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative #48063

I am also facing the same issue and I don't see any solution for the issue. Why is the issue closed?

It should be opened
On Fri, Mar 27, 2020, 18:11 PotholeProject<EMAIL_ADDRESS>wrote:

I am also facing the same issue and I don't see any solution for the
issue. Why is the issue closed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/28651#issuecomment-605053225,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJEI6SLNWLBQ5DYQTQNX7DRJS6YVANCNFSM4G24UVMQ
.

Same issue here  :(
W/FlutterJNI(12708): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: plugins.flutter.io/firebase_auth. Response ID: 0

Same issue for me too.
I'm using the package: https://pub.dev/packages/admob_flutter
To press the return button to close the app while an advertising banner is on screen make crash the app with the same log as above.

same issue. using the camera plugin.
the devices are samsung and xiaomi.

Same issue for me too.
I'm using the package: https://pub.dev/packages/admob_flutter
To press the return button to close the app while an advertising banner is on screen make crash the app with the same log as above.

same issue brother...

I am experiencing this problem as well running a Flutter app with Google Maps, Firestore, geolocation, and admob plugins.
java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
    at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:222)
    at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:543)
    at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:295)
    at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:35)
    at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:141)
    at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:206)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loop(Looper.java:214)
    at android.app.ActivityThread.main(ActivityThread.java:7073)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:965)

hi @matthew-carroll , I have the same problem. I configured the back button :
- no history: main activity will finish (call finish() method.).
After that I reopend the app => the app crashed.
I received a FATAL EXCEPTION:
java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:227)
at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:554)
at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:274)
at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:38)
at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:145)
at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:206)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:226)
at android.app.ActivityThread.main(ActivityThread.java:7212)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:576)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:956)

Looks like a collection of different issues going on here. Looking at a couple of the stack traces, they generally look like our engine code not thoroughly cleaning up callbacks when FlutterEngine.destroy -> flutterJNI.detachFromNativeAndReleaseResources is called. When those callbacks come back after the engine is destroyed it crashes.
@GaryQian would you like to make a comb on our engine code to clean up some of these dangling callbacks? The various stack traces above should offer hints on all the remaining handles.

hi
getting below issue with Flutter (Channel unknown, v1.17.1)
Fatal Exception: java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native.
at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:222)
at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:543)
at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:295)
at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:35)
at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:141)
at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:203)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5421)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
image
$ flutter doctor -v
[✓] Flutter (Channel unknown, v1.17.1, on Linux, locale en_US.UTF-8)
• Flutter version 1.17.1 at /home/cirrus/sdks/flutter
• Framework revision f7a6a79 (3 days ago), 2020-05-12 18:39:00 -0700
• Engine revision 6bc433c6b6
• Dart version 2.8.2
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /opt/android-sdk-linux
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = /opt/android-sdk-linux
• ANDROID_SDK_ROOT = /opt/android-sdk-linux
• Java binary at: /usr/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
[!] Connected device
! No devices available
! Doctor found issues in 3 categories

same issue with the flutter connectivity plugin
W/FlutterJNI(10176): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: plugins.flutter.io/connectivity_status. Response ID: 0

same issue with v1.17.2

Same issue with 1.17.3, using flutter_inappwebview and connectivity plugins.
Stack trace:
E/AndroidRuntime( 2950): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native. E/AndroidRuntime( 2950): 	at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:222) E/AndroidRuntime( 2950): 	at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:543) E/AndroidRuntime( 2950): 	at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:295) E/AndroidRuntime( 2950): 	at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:35) E/AndroidRuntime( 2950): 	at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:141) E/AndroidRuntime( 2950): 	at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:209) E/AndroidRuntime( 2950): 	at android.os.Handler.dispatchMessage(Handler.java:108) E/AndroidRuntime( 2950): 	at android.os.Looper.loop(Looper.java:166) E/AndroidRuntime( 2950): 	at android.app.ActivityThread.main(ActivityThread.java:7425) E/AndroidRuntime( 2950): 	at java.lang.reflect.Method.invoke(Native Method) E/AndroidRuntime( 2950): 	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245) E/AndroidRuntime( 2950): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)

I have same problem when using mapbox_gl and flutter version 1.17.4 in debug mode not in release mode.

same issue with v1.17.4, detected on dashboard in play store

The same issue in v1.17.4, app crashes on pressing the back button, using similar dependencies, as mentioned in earlier comments.

I have the same issue by pressing the back button.

Same issue with 1.17.3, using flutter_inappwebview, firebase_remote_config and connectivity plugins.
Stack trace:
E/AndroidRuntime( 2950): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native. E/AndroidRuntime( 2950): at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:222) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:543) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:295) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:35) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:141) E/AndroidRuntime( 2950): at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:209) E/AndroidRuntime( 2950): at android.os.Handler.dispatchMessage(Handler.java:108) E/AndroidRuntime( 2950): at android.os.Looper.loop(Looper.java:166) E/AndroidRuntime( 2950): at android.app.ActivityThread.main(ActivityThread.java:7425) E/AndroidRuntime( 2950): at java.lang.reflect.Method.invoke(Native Method) E/AndroidRuntime( 2950): at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245) E/AndroidRuntime( 2950): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)

Hello, did you resolve this issue. I met the same issue when using InAppWebView.

Same issue with 1.17.3, using flutter_inappwebview, firebase_remote_config and connectivity plugins.
Stack trace:
E/AndroidRuntime( 2950): java.lang.RuntimeException: Cannot execute operation because FlutterJNI is not attached to native. E/AndroidRuntime( 2950): at io.flutter.embedding.engine.FlutterJNI.ensureAttachedToNative(FlutterJNI.java:222) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.FlutterJNI.markTextureFrameAvailable(FlutterJNI.java:543) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer.markTextureFrameAvailable(FlutterRenderer.java:295) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer.access$300(FlutterRenderer.java:35) E/AndroidRuntime( 2950): at io.flutter.embedding.engine.renderer.FlutterRenderer$SurfaceTextureRegistryEntry$1.onFrameAvailable(FlutterRenderer.java:141) E/AndroidRuntime( 2950): at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:209) E/AndroidRuntime( 2950): at android.os.Handler.dispatchMessage(Handler.java:108) E/AndroidRuntime( 2950): at android.os.Looper.loop(Looper.java:166) E/AndroidRuntime( 2950): at android.app.ActivityThread.main(ActivityThread.java:7425) E/AndroidRuntime( 2950): at java.lang.reflect.Method.invoke(Native Method) E/AndroidRuntime( 2950): at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245) E/AndroidRuntime( 2950): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)

Hello, did you resolve this issue. I met the same issue when using InAppWebView.

Nope, just waiting for the official fix.

https://github.com/flutter/engine/pull/19558 Has landed, those with the markTextureFrameAvailable version of this crash, can you please verify the fix? The change is on master channel.

After a quick read through this issue, there have been 3 different crashes and 3 different fixes. It seems that the markTextureFrameAsAvailable one is the last of the remaining crashes, and if confirmed resolved, I think we can (re)close this issue.

Actually, the fix has not yet rolled into master, the roll seems to be slightly backed up. Will post here when it is available.

flutter/engine#19558 has rolled into master. Should be ready for trying out now.

I'm still experiencing this issue:
Flutter 1.20.0-8.0.pre.125 • channel master • https://github.com/flutter/flutter.git
Framework • revision 9c4a5ef1ed (10 hours ago) • 2020-07-15 21:41:27 +0100
Engine • revision 774ae0313d
Tools • Dart 2.9.0 (build 2.9.0-21.0.dev 89fe12b12a)

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.20.0-8.0.pre.125, on Mac OS X 10.15.5 19F101, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
[✓] Android Studio (version 4.0)
[!] IntelliJ IDEA Community Edition (version 2020.1.1)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (1 available)

I can sometimes reproduce the "FlutterJNI was detached" message by just pressing back from the screen which triggered communication with the native side, like the sensors package, and backing up until the app is sent to the background, then the message would appear.

Thanks @GaryQian ! I'm not getting the RuntimeException anymore, but if I re-open the app and navigate back from a specific page, I get a
Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: plugins.flutter.io/cloud_firestore. Response ID: 0
$ flutter doctor -v:
[✓] Flutter (Channel master, 1.20.0-8.0.pre.125, on Linux, locale en_US.UTF-8)
    • Flutter version 1.20.0-8.0.pre.125 at /home/guilherme/Downloads/flutter
    • Framework revision 9c4a5ef1ed (16 hours ago), 2020-07-15 21:41:27 +0100
    • Engine revision 774ae0313d
    • Dart version 2.9.0 (build 2.9.0-21.0.dev 89fe12b12a)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/guilherme/Android/Sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /home/guilherme/Downloads/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /home/guilherme/Downloads/android-studio
    • Flutter plugin version 44.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.46.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.12.2

[✓] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 10 (API 29) (emulator)
    • Web Server (web)                   • web-server    • web-javascript • Flutter Tools
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 83.0.4103.116

• No issues found!

Is this causing any unexpected behavior? This warning was introduced in flutter/engine#8170 which fixed the platform message version of this bug and should just reflect the detached JNI state.

@markfili Can you try a flutter upgrade before trying again? It looks like your revision was from 10hrs ago from when you posted, which may not include the necessary changes.

Is this causing any unexpected behavior? This warning was introduced in flutter/engine#8170 which fixed the platform message version of this bug and should just reflect the detached JNI state.

Apparently not ;) Thanks for the clarification!

It looks like the 3 version of this bug reported here all have appropriate fixes, I will close this bug for now, please feel free to comment with any additional issues anyone sees regarding this and we can re-open.

When can we expect this to be made available in the stable channel?

Generally, stable releases are quarterly and beta releases are monthly. I don't have an immediate release date, but you can generally add a few months to the previous stable release. This is probably not hotfix worthy, but if enough people want it as a hot fix, we can consider it.
In the meantime, the change should soon be available on dev and master channels, and we welcome you to try it there.

@GaryQian What is the process to request a hotfix? Our users are experiencing crashes using our app https://play.google.com/store/apps/details?id=com.grab.merchant&hl=en and it is affected their businesses in terms of revenue generation.

@edeortuzar you need to try this on master channel. It has not made it to stable yet.

@fadrizul I will submit this for hotfix consideration

@fadrizul I will submit this for hotfix consideration

What version will the next stable be? and when will there be a new stable? I've seen 1.18,<IP_ADDRESS> on beta for a long time. 1.18 for more than 2 months. still not been made to stable. I'm a little confused.

@GaryQian any new updates from your side because the issue affected our users

This issue happened with me when i displayed an Interstitial Ads and while press back to close the App, the crash happened on background. So i disposed the Ad and this issue didn't happen. I published a new release but still this issue happened so may be something like Interstitial behavior caused the issue. any support ????

still happened also on flutter 1.20
On Tue, Aug 11, 2020 at 11:13 AM BeshoyAdelHemaya<EMAIL_ADDRESS>wrote:

This issue happened with me when i displayed an Interstitial Ads and while
press back to close the App, the crash happened on background. So i
disposed the Ad and this issue didn't happen. I published a new release but
still this issue happened so may be something like Interstitial behavior
caused the issue. any support ????
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/28651#issuecomment-671799594,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJEI6VIQZ3PUFRHVYJJ6E3SAD4TRANCNFSM4G24UVMQ
.

Why is this issue closed? I'm experiencing this bug on Android 10+ with the latest Flutter 1.20.1 (stable).

Same issue

Same here, but the weird thing is that it is just happening in release build not in debug build.
It looks related to AudioService Plugin after stopping the service
2020-08-12 15:05:34.072 2494-7425/? D/AudioService: setBluetoothA2dpOn false 2020-08-12 15:05:34.073 2494-3287/? D/AudioSystem-JNI: setForceUse (1,10) 2020-08-12 15:05:34.073 2246-2246/? D/APM_AudioPolicyManager: setForceUse() usage 1, config 10, mPhoneState 0 2020-08-12 15:05:34.085 25992-25992/? W/FlutterJNI: Tried to send a platform message response, but FlutterJNI was detached from native C++. Could not send. Response ID: 19 2020-08-12 15:05:34.085 25992-25992/? D/AndroidRuntime: Shutting down VM 2020-08-12 15:05:34.086 25992-25992/? E/AndroidRuntime: FATAL EXCEPTION: main     Process: com.mtheorysoft.twitterapitabbed, PID: 25992     java.lang.NullPointerException: Attempt to invoke virtual method 'void d.a.b.a.j.a(java.lang.String, java.lang.Object)' on a null object reference         at c.g.a.a$d.run(Unknown Source:10)         at android.os.Handler.handleCallback(Handler.java:790)         at android.os.Handler.dispatchMessage(Handler.java:99)         at android.os.Looper.loop(Looper.java:164)         at android.app.ActivityThread.main(ActivityThread.java:6626)         at java.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:811)

Sorry, my issue was related to Audio_Service interaction with Flutter_tts plugins. I solved the problem following the following instructions:
https://github.com/dlutton/flutter_tts/issues/149#issue-674593278

is this problem fixed? i'm getting Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: plugins.flutter.io/firebase_database when pressing the back button to exit from the app.

I am facing same issue. I am using Google Maps and Location plugins. When I open the screen that get user location, everything is working fine. But when I close the app through pressing back button and start again , I am getting a warning message every second and I think that  it is not a good thing as far as performance and battery drain.
Here my flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.23.0-8.0.pre.165, on Mac OS X 10.15.6 19G2021
    x86_64, locale en-TR)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.1)
[✓] Connected device (1 available)

• No issues found!
yusufnacar@yusufs-mbp ~ % flutter doctor - v
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.23.0-8.0.pre.165, on Mac OS X 10.15.6 19G2021
    x86_64, locale en-TR)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.1)
[✓] Connected device (1 available)

• No issues found!

And it is the message which I am facing every second
W/FlutterJNI( 4383): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: lyokone/locationstream. Response ID: 0

Maybe you need to close the reference to the Location or Map API somehow.
Or put a completer to check that the status of the API reference is correct when the back button is pressed and if not await to be complete.
Gracias,
Saludos,
Martin.
En 20 de noviembre de 2020 06:10, en 06:10, yusufnacar<EMAIL_ADDRESS>escribió:

I am facing same issue. I am using Google Maps and Location plugins.
When I open the screen that get user location, everything is working
fine. But when I close the app through pressing back button and start
again , I am getting a warning message every second and I think that
it is not a good thing as far as performance and battery drain.
Here my flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.23.0-8.0.pre.165, on Mac OS X 10.15.6
19G2021
   x86_64, locale en-TR)

[✓] Android toolchain - develop for Android devices (Android SDK
version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.1)
[✓] Connected device (1 available)

• No issues found!
yusufnacar@yusufs-mbp ~ % flutter doctor - v
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.23.0-8.0.pre.165, on Mac OS X 10.15.6
19G2021
   x86_64, locale en-TR)

[✓] Android toolchain - develop for Android devices (Android SDK
version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.1)
[✓] Connected device (1 available)

• No issues found!

And it is the message which I am facing every second
W/FlutterJNI( 4383): Tried to send a platform message to Flutter, but
FlutterJNI was detached from native C++. Could not send. Channel:
lyokone/locationstream. Response ID: 0

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/flutter/flutter/issues/28651#issuecomment-731042735

I'm having the same issue as well, for me it affects the Quickblox package. What's the status of the hotfix?
W/FlutterJNI( 9071): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: FlutterQBChatChannel/RECEIVED_NEW_MESSAGE. Response ID: 0

W/FlutterJNI( 3517): Tried to send a platform message response, but FlutterJNI was detached from native C++. Could not send. Response ID: 9
same here using pusher_client
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.19042.746], locale ar-IQ)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.52.1)
[√] Connected device (1 available)
! Doctor found issues in 1 category.

W/FlutterJNI( 3517): Tried to send a platform message response, but FlutterJNI was detached from native C++. Could not send. Response ID: 9
same here using pusher_client
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.19042.746], locale ar-IQ)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.52.1)
[√] Connected device (1 available)
! Doctor found issues in 1 category.

https://github.com/flutter/flutter/issues/28651#issuecomment-744396559
am also facing the same issue, when I clear the app from background,  am getting this message and then QuickBlox services has been stopped after this message

Same issue here. For me it happens when using just_audio and firebase_auth
W/FlutterJNI(20011): Tried to send a platform message response, but FlutterJNI was detached from native C++. Could not send. Response ID: 45

i got same error on package adhara_socket_io
"W/FlutterJNI(20116): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: adhara_socket_io:event_streams#6. Response ID: 0"

package com.gogappi.consumer
import androidx.annotation.NonNull;
import io.flutter.embedding.android.FlutterActivity
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.plugins.GeneratedPluginRegistrant
class MainActivity: FlutterActivity() {
override fun configureFlutterEngine(@NonNull flutterEngine: FlutterEngine) {
GeneratedPluginRegistrant.registerWith(flutterEngine);
}
}

Same issue here using "camera" plugin
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.2.1, on Microsoft Windows [VersiÃ³n 10.0.10586], locale es-VE)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.56.2)
[√] VS Code, 64-bit edition (version 1.55.2)
[√] Proxy Configuration
[√] Connected device (2 available)
• No issues found!
Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: flutter.io/cameraPlugin/device. Response ID: 0


Unescape to get plain text

Is there any methods to achieve this as in
https://github.com/slack-ruby/slack-ruby-client
We basically get the plain text from html
`Slack::Messages::Formatting.unescape('Hello & <world>'))
=> 'Hello & '
Slack::Messages::Formatting.unescape('Hey <@U024BE7LH|bob>, did you see my file?'))
=> 'Hey @bob, did you see my file?'
Slack::Messages::Formatting.unescape('Hey <@U02BEFY4U>'))
=> 'Hey @U02BEFY4U'
Slack::Messages::Formatting.unescape('This message contains a URL http://foo.com/'))
=> 'This message contains a URL http://foo.com/'
Slack::Messages::Formatting.unescape('So does this one: http://www.foo.com|www.foo.com'))
=> 'So does this one: www.foo.com'
Slack::Messages::Formatting.unescape('mailto:bob@example.com|Bob'))
=> 'Bob'
Slack::Messages::Formatting.unescape('Hello <@U123|bob>, say hi to <!everyone> in <#C1234|general>'))
=> 'Hello @bob, say hi to @everyone in #general'
Slack::Messages::Formatting.unescape('Hello <@U123|bob> > file.txt'))
=> 'Hello @bob > file.txt'
Slack::Messages::Formatting.unescape('“hello”'))
=> '"hello"'
Slack::Messages::Formatting.unescape('‘hello’'))
=> "'hello'"`

despite some of those transforms being incorrect.... no currently not. though I do have a version lying around to get someone started if they wanted to do the work.

@james-lawrence I'd be happy to give this a go, I guess :)

if you want code to get started, here is a custom lexer/parser I've written, its obviously very customized to my use case but the lexer is self contained and the parser should be easy to change for your uses:
parsing-slack.zip


refactor(vehicle_cmd_gate): remove old emergency topics (#2403)

Description

cherry-pick from autowarefoundation/autoware.universe

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta/v0.6.0@06ddd89). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff               @@
##             beta/v0.6.0     #204   +/-   ##
==============================================
  Coverage               ?   10.48%
==============================================
  Files                  ?     1248
  Lines                  ?    91219
  Branches               ?    21013
==============================================
  Hits                   ?     9566
  Misses                 ?    71466
  Partials               ?    10187

Flag
Coverage Δ

*Carryforward flag

differential
18.60% <0.00%> (?)

total
10.46% <0.00%> (?)

Carriedforward from 6abed14

*This pull request uses carry forward flags. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Improve PendingTask developer experience when overriding.

When you extend PendingTask, it is not easy to tell what you need to add to get it to work (some fields are optional, some do not force you to override, etc).
I want to make creating PendingTasks really easy by extending a class and get up and running fast.

The problem with this class is that I cannot mark it as abstract because of SQLite.
Maybe there is a way for me to create a PendingTask class that is saved into SQLite, have an abstract subclass of PendingTask that is designed for the improved functionality that users of the library extend instead. Anyone can extend PendingTask if they need that power but you should not need to.

Ways to improve this class:

[ ] Empty constructor. It's confusing having a constructor that has fields in it such as id and created_at that are only there for sqlite purposes but not used by the user.
[  ] Abstract functionality such as helping the user determine if their task manually runs or not. Help the subclasses understand what info Wendy needs to know about the class. You should be able to extend PendingTask and instantly get helped into creating the task. runTask() should be abstract as well.

Done. Will be added to project in the next PR from the branch big-refactor


删除值时，界面上显示已删除干净，但是实际最后一个字符无法删掉

Describe the bug

Steps to reproduce
按照官方文档正常引入使用
Package Info
^2.1.7

Validations

[X] Is it the latest version?
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[ ] The provided reproduction is a minimal reproducible example of the bug.

升级到最新版吧，这个版本有 bug


Fix #400 - add docs to readthedocs mkdocs.yml

This pr fixes issue #400 by adding missing doc files to the mkdocs.yml used to build the readthedocs site.

Lgtm.


The effect of voxel size on the final result

Hi, do you know the effect of voxel size on the final result?
big better or small better?
thanks!

to my  best knowledge
if you use a big voxel size like [0.5,0.5,2]，the number of voxels  must less than that of  the small voxel size, which definitely increase the infer speed , and the space information about the object will loss much  at the same time ,so the accuracy will decrease ,the voxel size need to well tune to balance the efficiency and accuracy,


Add model builder build operations

Context

Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

I threw this together as a POC. it looks like this in the IDE:


Get-AgentJobStep Integration Tests

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[x] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Adding some tests on a Saturday morning.
Screenshots

darn, passed on your side, failed on appveyor

I'll take a peek .. give me a few
On Sat, May 25, 2019, 9:50 AM Chrissy LeMaire<EMAIL_ADDRESS>wrote:

darn, passed on your side, failed on appveyor
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/pull/5596?email_source=notifications&email_token=AAHPS6TDRJ2B3JTXYHWZ4XDPXE725A5CNFSM4HPUP5AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWHSHAY#issuecomment-495920003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHPS6W2C6Z3VA7N5MIN2LTPXE725ANCNFSM4HPUP5AA
.

@potatoqualitee so this ran fine against instance2 (I noticed the other AgnetJob tests were using that). Is this a version issue, instance1 being 2008R2 or is there no agent or something on that instance?

The SQL Agent is only on Instance2 from what I recall..

Ok - that would make a lot of sense. It didn't manage to get any job information when running against instance1.

The only agents that will include Agent are 2016 and 2017 instance. They have Dev Edition, the 2008 one is just express.

Good deal. Is there documentation on the Appveyor setup, for example versions/editions available? I looked at the Appveyor lab repo but didn't know what I was looking at.

HECK YAHH

I'm working on documentation for it all. We have some here dbatools.io/appveyor but I'll trying to expand that out a bit more.


Question: Is it possible to migrate to another nfs server ?

Hi,
I have a question, and i don't find any answer. Maybe you can help me ...
In fact I have to migrate my pvc to another NFS Server.
All datas will remain exactly the same (same name same files same folders... ) the only change will be the IP of the server.
I tried to upgrade the chart with the new IP : nfs.server.ip parameter but it did not change existing volumes.
Can you help me to figure out how to do the manipulation ? I tried to change the IP directly in the PV but nothing work.
I know it is a question that is maybe not in your scope but maybe you have an idea ...

Thanks for reporting the issue!
This repo is no longer being maintained and we are in the process of archiving this repo. Please see https://github.com/kubernetes/org/issues/1563 for more details.
If your issue relates to nfs provisioners, please create a new issue in https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner or https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.
Going to close this issue in order to archive this repo. Apologies for the churn and thanks for your patience! :pray:


add TreeSelect component or support select with hierarchy

[ v] This is not a v0.x issue.
[v ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

like a normal select but with hierarchy

@eladmotola I"m sorry, this feature is outside of our scope. We focus on the building blocks people are very likely to need.

hey, me again.
i know you close this issue but Im banging my head and i dont have any clue how to continue, maybe you can help me.
i have a component that has a select:
 <Select onChange={this.fire} >             <MenuItem value="">               None             </MenuItem>             <MenuItem value={10}>Ten</MenuItem>             <MenuItem value={20}>Twenty</MenuItem>             <MenuItem value={30}>Thirty</MenuItem>             <MyCustomMenu />            </Select>
this.fire function only do console.log(event.target.value)
the <MyCustomMenu />  component look like that:
`class MyCustomMenu extends Component {
constructor(props) {
super(props)
this.state = {
isOpen: false
}
}
changeme = () => {
    this.setState(prevState => ({
        isOpen: !prevState.isOpen
    }));
}

render() {
    const { isOpen } = this.state
    return (
        <Fragment>
            <MenuItem value="Drafts" >
                <ListItemIcon onClick={this.changeme} >
                    {isOpen ? <ArrowLeft /> : <ArrowDownward />}
                </ListItemIcon>
                <ListItemText inset primary="Drafts" />
            </MenuItem>
            {isOpen &&
                <Fragment>
                    <MenuItem value={40}>40</MenuItem>
                    <MenuItem value={50}>50</MenuItem>
                </Fragment>
            }
        </Fragment>
    );
}

}
export default MyCustomMenu;
`
now, when fire function is firing (nice one), I can have only the value of the 10,20,30. what i dont get its "Draft",40,50. what im doing wrong here?
thanks for your help!

We have moved the discussion to https://github.com/mui-org/material-ui-x/issues/514


spellcheckers/dictionaries are almost invisible in Thunderbird (too hard to reach)

This is from mozilla/addons/issues/733:
Describe the problem and steps to reproduce it:
I opened Thunderbird > Add-ons > Explore Addons > addons.mozilla.org (over one of the links there) -> search "english" or "deutsch"
What happened?
The search returned no result or just normal add-ons
What did you expect to happen?
I clicked in the navigation on
more -> Dictionaries & Language Packs -> The language(s) I wanted.
Now suddenly german/english dictionaries appear in the search.
Before they didn't for some reason.
I don't have the issue in Firefox, when I open the addon domain. (dictionaries are always part of the search results, when the search term fits)
But everytime I open the Page in Thunderbird (until I visited more -> language packs)
They are also way too hidden, considering how useful they are when writing mails.
It would be nice to see them listed next to themes and apps on the local "explore add-ons" page.
Also there are no backwards/forwards buttons when browsing on addons.mozilla.org in Thunderbird.
Regards,
Djfe
Anything else we should know?
I know these are partly Thunderbird bugs, but they are all related to addons.mozilla.org , so you and the Thunderbird team probably have to join efforts anyways, so I would rather report it here :)

That is what I see the above in Thunderbird addon manager and is I assume the basis of most of your comments.  I click dictionaries and search and all works well.  We are trying to encourage all add-ons and dictionaries to be installed via the appropriate location in Thunderbird.  Personally I suggest you use the link in options.
Options > composition > Spelling has a link to dictionaries and language packs which I generally recommend as it is not a search,  and opens https://addons.thunderbird.net/thunderbird/language-tools/ in a Thunderbird tab from which install is two clicks away, one to select the dictionary and one to click the install button. Using the options method each and every selection I make opens a new tab, negating the need is any way for a back or forward button.


Add support for AWS Transfer Family

Adding support for AWS Transfer family in both the product and also into the usage file.
Terraform resources:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/transfer_server
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/transfer_ssh_key
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/transfer_user
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/transfer_access
Pricing: https://aws.amazon.com/aws-transfer-family/pricing/
Note for community:
Please 👍 if you'd like to upvote this or receive updates.
See our contributing guide if you'd like to help with this issue!

This has been merged to master and will go live with the next release.

@bourbonfgiles @robh007 @PatMyron 0.9.13 is released.  Thanks @vdmgolub!


CI: Run on pushes and PRs to 0.x maintenance branches

Run the CI also on pushes and pull request to the 0.x maintenance branches (0.3, 0.4 etc.)
For this PR to have effect, it needs also to be merged to the 0.3 and 0.4 branches. Are separate PRs preferred, or can this commit be cherry picked?

Coverage decreased (-0.5%) to 73.515% when pulling d3199d580c71787aad8a872dc3d8f06919a9fbab on EwoutH:patch-34 into cae1980267937fa352be29edc95cb8d77ee4cbfb on xiph:master.

Coverage decreased (-0.5%) to 73.515% when pulling d3199d580c71787aad8a872dc3d8f06919a9fbab on EwoutH:patch-34 into cae1980267937fa352be29edc95cb8d77ee4cbfb on xiph:master.

Thanks for merging. Would you like seperate PRs with this commit for the 0.3 and 0.4 branches?

Thanks for merging. Would you like seperate PRs with this commit for the 0.3 and 0.4 branches?

Yes please

Yes please

The CI on 0.3 is already modified to run on 0.3, so I only needed to cherry-pick 94993a7763c7fd95a738ed1a339b6ebeb5e523e5 to 0.4. Opened a PR here: #2654

The CI on 0.3 is already modified to run on 0.3, so I only needed to cherry-pick 94993a7763c7fd95a738ed1a339b6ebeb5e523e5 to 0.4. Opened a PR here: #2654


Clean up building from source

The build from source option is typically used when developing code which is then deployed to the VMs. Given that it doesn't make sense to not build just because the _output directory is present. Also when building from source there is no reason to compute KUBERNETES_VERSION.
Stop setting path by default in the makefile as that needs to be passed explicitly by the user.

/retitle WIP: Always build from source

/retitle Clean up building from source

/lgtm
/approve


"export" not supported in IE11

Hi there,
On May 16 you added "export" declarations in the code. As I want to use this polyfill in IE11 which is the most frequent use case, I guess. IE11 does not support "export" (ES6 modules in general).
Cheers,
Andreas

See https://github.com/github/fetch/issues/656#issuecomment-420219378


Audit, exception log tibet2

The xslt which is responible for making the output of the ladybug gets an bitstream and should be an soap message in order to make the xslt understand it's xpaths.
Tibet2 has extra options in the ladybug under view: exceptionlog and auditlog:

Reporter
Tarik

To Reproduce
Steps to reproduce the behavior:

Put the .ttr file in any Frank and look at the column message

Screenshots
When doing the test in framework 7.6 we get this

When doing the same in framework 7.5.1 we get this

Configuration
This is the location of the xslt used:
https://github.com/ibissource/iaf/blob/master/ladybug/src/main/resources/TestTool/xsl/Tibet2.xsl
Input
This s a trail in the 7.6 framework
Table AUDITLOG_fail_493.zip
This is the message when sed in 7.5.1
Table AUDITLOG_ok_301.zip

Could you provide ladybug reports of the creation of these records too?


Make render tests work on more devices

By setting a device pixel ratio of 1.0 and increasing the tolerance for raster reprojection tests, the render tests now also run from the console on OSX devices with retina display.

Thanks, please merge.


Update TravisCI ciManagement reference

https://travis-ci.org is being phased out in favor of https://travis-ci.com.
See:

https://docs.travis-ci.com/user/migrate/open-source-repository-migration

Depends on https://github.com/PicnicSupermarket/oss-parent/pull/107.


functionality mostly complete

few bugs, needing to style

600 lines of code 🥲🥲🥲 so beautiful. Can't wait to play it tomorrow 🤙 Merging.


Magento 2.4 (latest) Could not validate a connection to Elasticsearch. No alive nodes found in your cluster

Describe the bug
I installed ddev on my machine and used Magento 2 Quickstart steps to install latest Magento version but I got the error while setting up the magento.
To Reproduce
Steps to reproduce the behavior:

Go to 'Magento 2 Quickstart'
Run commands step by step
Run magento setup command bin/magento setup:install  --db-host=db --db-name=db --db-user=db --db-password=db  --admin-firstname=Magento --admin-lastname=User<EMAIL_ADDRESS>--admin-user=admin --admin-password=admin123 --language=en_US
See error

Expected behavior
Magento setup should complete without any error
Screenshots

Version and configuration information (please complete the following information):

Host computer OS and Version: macOS Catalina
Docker Desktop version if on macOS or Windows: <IP_ADDRESS>
ddev version information: v1.15.3

Additional context
We need one more container for elasticsearch for Magento 2.4.x.

You must install and configure Elasticsearch 7.6.x before upgrading to Magento 2.4.x.
Magento 2.4.x is tested with Elasticsearch 7.6.x only. You can use other 7.x versions at your discretion, but we recommend using the tested version of Elasticsearch.
More info here

As you say, elasticsearch is not included by default, but there is a recipe for it in ddev-contrib. Previous versions of Magento haven't had it enabled by default though.

Thanks @rfay
I was looking for the recipe which you have mentioned. That solves this issue.

Thanks @VivekShingala - But previously the quickstart worked out of the box. You're saying it does not with Magento 2.4?
Obviously Elasticsearch is a preferred add-on. But if it fails on initial start because of expecting elasticsearch the quickstart should be improved.

Yes, quickstart breaks when we install 2.4 and elasticsearch container should be the part of it so that the installation go smooth.

Reopening for docs.


Updated docu for VM controls in Flex

Added a warning not to retroactively remove a VM control if adaptations already exist (and the opposite scenario)

Thank you for your feedback! We’ll look into it and come back to you if we have any questions.

Thank you for your feedback! It will go into the next version.


Allow concatenation of both in-memory and on-disk datasets

This is a prerequisite for the addition of the add_item feature (see #1870).
Currently there is one assumption that we would need to change: a dataset is either fully in memory (dataset._data_files is empty), or the dataset can be reloaded from disk (using the dataset._data_files).
This assumption is used for pickling for example:

in-memory dataset can just be pickled/unpickled in-memory
on-disk dataset can be unloaded to only keep the filepaths when pickling, and then reloaded from the disk when unpickling

Maybe let's have a design that allows a Dataset to have a Table that can be rebuilt from heterogenous sources like in-memory tables or on-disk tables ? This could also be further extended in the future
One idea would be to define a list of sources and each source implements a way to reload its corresponding pyarrow Table.
Then the dataset would be the concatenation of all these tables.
Depending on the source type, the serialization using pickle would be different. In-memory data would be copied while on-disk data would simply be replaced by the path to these data.
If you have some ideas you would like to share about the design/API feel free to do so :)
cc @albertvillanova

I started working on this. My idea is to first add the pyarrow Table wrappers InMemoryTable and MemoryMappedTable that both implement what's necessary regarding copy/pickle. Then have another wrapper that takes the concatenation of InMemoryTable/MemoryMappedTable objects.
What's important here is that concatenating two tables into one doesn't double the memory used (total_allocated_bytes() stays the same).

Hi @lhoestq @albertvillanova,
I checked the linked issues and PR, this seems like a great idea. Would you mind elaborating on the in-memory and memory-mapped datasets?
Based on my understanding, it is something like this, please correct me if I am wrong:

For in-memory datasets, we don't have any dataset files so the entire dataset is pickled to the cache during loading, and then whenever reqiured it is unpickled .
For on-disk/memory-mapped datasets, we have the data files provided, so they can be re-loaded from the paths, and only the file-paths are stored while pickling.

If this is correct, will the feature also handle pickling/unpickling of a concatenated dataset? Will this be cached?
Thanks,
Gunjan

Hi ! Yes you're totally right about your two points :)
And in the case of a concatenated dataset, then we should reload each sub-table depending on whether it's in-memory or memory mapped. That means the dataset will be made of several blocks in order to keep track of what's from memory and what's memory mapped. This allows to pickle/unpickle concatenated datasets

Hi @lhoestq
Thanks, that sounds nice. Can you explain where the issue of the double memory may arise? Also, why is the existing concatenate_datasets not sufficient for this purpose?

Hi @lhoestq,
Will the add_item feature also help with lazy writing during map/filter?

Can you explain where the issue of the double memory may arise?

We have to keep each block (in-memory vs memory mapped) separated in order to be able to reload them with pickle.
On the other hand we also need to have the full table from mixed in-memory and memory mapped data in order to iterate or extract data conveniently. That means that each block is accessible twice: once in the full table, and once in the separated blocks. But since pyarrow tables concatenation doesn't double the memory, then building the full table doesn't cost memory which is what we want :)

Also, why is the existing concatenate_datasets not sufficient for this purpose?

The existing concatenate_datasets doesn't support having both in-memory and memory mapped data together (there's no fancy block separation logic). It works for datasets fully in-memory or fully memory mapped but not a mix of the two.

Will the add_item feature also help with lazy writing (or no caching) during map/filter?

It will enable the implementation of the fast, masked filter from this discussion: https://github.com/huggingface/datasets/issues/1949
However I don't think this will affect map.


Update poetry check pre-commit revision to "1.4"

The pre-commit job in the test workflow no longer works. Updating the revision to "1.4" seems to fix it.

Fixed in https://github.com/hpcflow/hpcflow-new/commit/8d01183f86d1f8218b63481c52b6edbd0d23fc33 and https://github.com/hpcflow/matflow-new/commit/f02e678ca695713987f1bf5c93aea4288acf8cdd.