I am running Dart 2.0.0 with VSCode 1.26.1. I constantly see the following error written in Console under MacOS High Sierra 10.13.6:
nw_path_close_fd Failed to close guarded necp fd 6 [9: Bad file descriptor]
As soon as I close VSCode the dart process (and the error in the Console) goes away. Any ideas on why Dart is doing this? The offending library appears to be libsystem_network.dylib.
The dart process is any instance of a Dart VM running. VSCode will run a dart process for the realtime static analyzer, which feeds your warnings and errors panel. It may also be a Dart process that you launched from VSCode, the command-line, or another Dart process that the VSCode Dart plugin launches (other than the analyzer).
I can confirm that this issue does not occur when using IntelliJ IDEA and the Dart plugin. If you can isolate that it isn't the Dart code you are writing, I'd file a bug with the plugin repository: https://github.com/Dart-Code/Dart-Code/issues.
Related
Has anyone installed the latest concierge with the RedWeb SDK?
Since installing I can no longer save and have the program automatically compile the code. It will compile and then loops. Normally you save your file and it automatically compiles and responds with the ready and the localhost, etc... I have to kill the terminal session in VSC and restart a terminal session and do ngv run and it will work.
Note: This is the Concierge version released this week. We are developing specifically for RedWeb and not the desktop version which has a different SDK. Just curious if anyone is experience this with SabreRedWeb-SDK-21.5.5
I had issues with that version also. Sabre has just finalized version 21.6 SDK and it should be on the website soon. The newer version worked fine with all my testing so far.
Summary:
When I attempt to build and run my Uno WebAssembly on Ubuntu 20.04, it fails. The error cites a file or directory that doesn't exist.
Steps to reproduce:
Open Ubuntu 20.04 platform
Install .NET Core SDK 3.1.403
Follow the "Getting Started on VSCode" tutorial here
When you attempt to start the app with the .NET Core Launch configuration, note that the build fails.
Error Details:
/home/<user>/.nuget/packages/uno.wasm.bootstrap/1.3.4/build/Uno.Wasm.Bootstrap.targets(126,2): error : System.ComponentModel.Win32Exception (2): No such file or directory [/home/<user>/Projects/uapp/uapp.Wasm/uapp.Wasm.csproj]
What I've tried
My knowledge of Uno Platform is approximately 1 day old. I'm not sure I understand enough about it to even know what to try, but I have done these things:
Run dotnet run from within the uapp.Skia.Gtk, which successfully opened the window I expected to see.
Run dotnet run from within uapp.Wasm, which resulted in the error described above.
Look on the documentation for clues on why the file might not be found on a fresh template that's not been modified (I could not find anything)
Question:
What should I be doing differently to get the Web Assembly to build and display the app correctly?
EDIT: The file in the error does exist, precisely in the path in the error.
You're hitting an error that may happen when building with some native components, like SQLite or Skia.
To fix this, you'll need to execute the dotnet-setup.sh installation script which is not yet run automatically.
This script installs .NET Core, mono and ninja, on ubuntu-alike systems.
A development build works fine, but when I try a release build, it crashes immediately on start due to the Proguard.
I installed Crashlytics to try getting any error but it does not show any error (crashlytics works).
Might be important to add:
Just added Firebase and Facebook SDK.
How should the proguard.txt file look like?
Thank you in advance.
ran build without fail yesterday but suddenly firebase issue has occurred. what should i set for this issue?
i tried the following
cordova.system.library.4=com.google.firebase:firebase-core:16.0.9
cordova.system.library.5=com.google.firebase:firebase-messaging:18.0.0
cordova.system.library.6=com.google.firebase:firebase-config:17.0.0
cordova.system.library.7=com.google.firebase:firebase-perf:17.0.2
link:
https://firebase.google.com/support/release-notes/android#update_-_may_31_2019
but that shows that
What went wrong:
The library com.google.firebase:firebase-iid is being requested by various other libraries at [[18.0.0,18.0.0]], but resolves to 19.0.0. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.
so i changed messaging version that
cordova.system.library.5=com.google.firebase:firebase-messaging:19.0.0
but also shows error
What went wrong:
Execution failed for task ':app:processDebugResources'.
Failed to execute aapt
ionic cordova build android
ionic cordova run android
I did what firebase shows me to do, but it hasn't been resolved.
thanks
Take a look at this thread: https://github.com/arnesson/cordova-plugin-firebase/issues/1081
In particular #dpa99c's comment
https://github.com/arnesson/cordova-plugin-firebase/issues/1081#issuecomment-503135862
I was having the same problem since the Firebase support update (June 17, 2019) but running through those steps in #dpa99c's comment worked for me.
In addition to this, if you are building for iOS as well then you may need to update to the latest version and install pod inside your iOS platform folder if you haven't done so already.
I am using Firebase Auth. I am working in unity 2018. I have dowloaded Quickstart-unity-Master. In that I am working Auth Section. I have download the latest googlservices.json file also, but when I try to build the Firebase auth in android, it shows the error
Gradle build Error.
Error Image
I have searched in Forum it Says Java greater 8 is not supported. I am using jdk1.8.0_171.
I have donwloaded varrious unity packages 2017 Versions.
I Installed 10 Different versions. In that one versions First time it builds and apk produced. But second time I build it shows the error. Gradle Build failed.
How can I solve the gradle Error.
Thanks and Regads
This error might not be related to Firebase at all. I have multiple projects where Gradle fails for some reason. Just try what happens when you switch the build system from Gradle to Internal. This works for my projects.