I upgraded to WebStorm 2019.3 a few days ago and now the bundled Material theme shows the error 'Incompatible with the current WebStorm version'. In the Marketplace tab the version of Material theme is 4.10.0 Dez. 01, 2019. As it is bundled I can't de-install it. Any hints how to rid of the error or this theme?
Screenshot of Settings - Plugins:
Has to be some glitch as that's a 3rd party plugin and JetBrains will NOT bundle such plugins (but may offer on fresh install). I've just installed trial of WebStorm 2019.3 on Windows and that plugin was offered as a custom install -- it's not bundled for sure.
Solution -- reinstall plugin to fix this issue. For this:
Close IDE
Locate plugins folder (check https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs to locate plugins folder that is specific for your OS)
Manually delete that plugin file (could also be a folder; depends on plugin)
Launch IDE and check if plugin is still listed there (should not be listed now)
Install Material Theme UI plugin again using Plugins screen
Related
I am unable to debug a Xamarin.iOS application out of JetBrains Rider 2022.2.2. This is the error that gets thrown when trying to deploy to the simulator:
error HE0004: Could not load the framework 'DVTITunesSoftwareServiceFoundation' (path: /Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/DVTITunesSoftwareServiceFoundation):
dlopen(/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/DVTITunesSoftwareServiceFoundation, 0x0001): Library not loaded: '#rpath/ContentDelivery.framework/Versions/A/ContentDelivery'
Referenced from: '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/DVTITunesSoftwareServiceFoundation'
Reason: tried: '/usr/lib/swift/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Library/Frameworks/Xamarin.iOS.framework/Versions/15.12.0.2/lib/mlaunch/mlaunch.app/Contents/MacOS/../Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/usr/lib/swift/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Library/Frameworks/Xamarin.iOS.framework/Versions/15.12.0.2/lib/mlaunch/mlaunch.app/Contents/MacOS/../Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/Applications/Xcode.app/Contents/SharedFrameworks/DVTITunesSoftwareServiceFoundation.framework/Versions/A/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file), '/System/Library/Frameworks/ContentDelivery.framework/Versions/A/ContentDelivery' (no such file)
I had the same problem.
Let me guess... You just upgraded to XCode14 and the corresponding Command Line Tools?
Downgrading XCode and Command Line Tools to 13.4.1 helped me.
What worked for me
Go To https://developer.apple.com/download/all/?q=command%20line%20tools
Download XCode and Command Line Tools for Xcode 13.4. Unpack Xcode (13.4.1) and rename it (for example Xcode 13) and place it parallel to Xcode (14) in the programfolder.
.
Then install the Command Line Tool.
Now in Xcode (still 14) > Preferences > Location > Command Line Tools, select version 13.4.1 instead of 14. You can see the Path for it is "Application/Xcode 13".
For safety restart tools, and it worked again...
Update: With the last update of Visual Studio, the downgrade was no longer necessary for me. Since then I can build the apps with XCode 14 and the corresponding command line tools without any problems. So I suggest upgrading Visual Studio to the latest version first.
Here is how I made it work:
Download the former version here (note: you need a developer account)
Double-click on the downloaded .xip file to install XCode 13.4.1
Rename the newly installed XCode application into Xcode.13.4.1.app and move it into your Applications folder
Open the usual XCode application and go to the preferences
In the locations tab you will be able to select XCode 13.4.1 for Command Line Tools
Redownload Visual Studio?
It turns out Microsoft released a brand new Visual Studio at some point.
We haven't been in our Xamarin project for a while and even though it said there were no updates, no Simulators were showing up.
Our Visual Studio said the version was 8.10.25 yet when I was reading the release notes, they referred to version 17.3.7.
Our team had to download Visual Studio again and then we saw the version updated to 17.3.7.
So check your version of Visual Studio and redownload the newest one. That's what fixed this issue for us.
Latest update fixed the issue for me.
I had the same issue, while searching for answer I found this thread,
writing this to confirm that I took the latest update on 9th nov(NET 7 SDK). Issue seems resolved with latest update.
There is a more elegant solution to this problem. You need to upgrade Xamarin.iOS manually. The releases are on GitHub 16.0.0.72 did the trick for me.
I have a multi module Android Compose project. One module is an android app, others are android libraries or kotlin libraries. I'm running AS Artic Fox 2020.3.1 Beta 5 on MacOS 11.4 Big Sur.
After a library upgrade (probably AGP to use compose, I don't remember when exactly) Android Studio started to show syntax errors everywhere, both in .kts and .kt files.
Compilation and execution are working fine, only those weird JDK errors are displayed.
Here are some examples :
in a .kt file from a kotlin library module, in a .kts file from the buildSrc module
It seems that there is an error with the JDK somewhere, but I don't understand how to fix it.
I Googled/StackOverflowed before posting here and I already tried :
to check the JDK used Project Structure > SDK Location > Gradle. It is using the Embedded JDK 11.0.10
to reinstall AS using Jetbrains Toolbox
to invalidate cache and restart
to clone my project again
to delete ~/.gradle
But none of those actions helped...
Thanks in advance !
Update 22/07
I tried to create a new empty Compose project with .kts support, but no luck, everything is in red
Because of a bug preventing to update, I updated manually to RC_1. Here is my current setup.
I tried to change from Embedded JDK to a separately installed OpenJDK 11 and reimport but not luck (#alexey-belkov suggestion)
I checked the logs but found nothing obvious (#andy suggestion)
ℹ️ Finally I tried to create a new empty Android project with only .gradle support, and no errors ! Could it be a kotlin script plugin problem ?
I have followed the instructions in https://github.com/mbats/eclipse-buildroot-bundle/wiki/Tutorial-:-How-to-activate-and-install-the-Buildroot-Eclipse-plugin-%3F for installing the plugin.
Buildroot's server for eclipse plugins (https://buildroot.org/downloads/eclipse/) does'nt contain plugin for eclipse MARS version (v4.5).
I tried to install the 'Luna' version (v4.4) plugin but I got my toolchain list corrupted.
I tried starting-up eclipse with the -clean flag in the 'eclipse.ini' file but it didnt help either.
How can I make eclipse "register" buildroot plugin for eclipse versions higher than 4.4 ?
The plugin supports at most Eclipse Luna at the moment. Work is on-going to support higher versions.
I've recently get update notification of android studio 2.3, after the update it's not opening any project and throwing error:
[plugin: com.darkklord.gradle.metric.core]
after downgrading and reinstalling i still have this issue, can anyone please help me on this topic ?
Download latest plugin from here: https://plugins.jetbrains.com/plugin/9197-android-gradle-metrics--checkstyle
Install Plugin manually from disk.
Restart Android Studio (The error will still occur)
Remove plugin in IDE.
Restart
You might also uninstall the refrenzed plugins Checkstyle and PMD
You need to change your dependency
classpath 'com.android.tools.build:gradle:3.1.0'
Sometimes you need to change name of project manually(look at AndroidStudioProjects folder) that you opened lastly.
After changing name, android studio will show all projects,
open one of them,
in file menu,
click open button,
then open your desire project (or change its name to its previous name)
change build:gradle plugin to:
classpath 'com.android.tools.build:gradle:3.3.2'
(in app gradle file)
I made sure that my Gradle version was compatible with my android gradle plug in. In my case I was using Gradle 6.0.1 and when I changed my android gradle plug in to version 3.5.3 the problem went away.
Project Structure----->> Project ------>> Android Gradle plug in version 3.5.3.
[https://docs.gradle.org/6.0.1/release-notes.html
[Java 14 and later versions are not yet supported.
Compatibility Notes
A Java version between 8 and 13 is required to execute Gradle.
Java 6 and 7 can still be used for compilation and forked test execution. Just like Gradle 5.x, any supported version of Java can be used for compile or test.
This version of Gradle is tested with
-------->>>>>>>>Android Gradle Plugin 3.4, 3.5 and 3.6
Kotlin 1.3.21 through 1.3.50
Other versions may or may not work.]]]]
I hope this helps
I try to install nodeclipse on Titanium Studio, I added the link http://www.nodeclipse.org/updates/, I got all the packages, but when I install them, Titanium warns me that lot of them already exist, and I let him install the other ones.
But after the installation ends, and restarting Titanium, i dont find the Node.js support.
That happened too on Aptana Studio.
here is the video showing that:
http://youtu.be/Lho06QBjRWY
Google drive pictures:
https://drive.google.com/folderview?id=0B-Iu7VFIRkh4VnNic0g5OHNIZzQ&usp=sharing
You don't need to install ALL plugins. E.g. latest Mylyn and EGit may be not compatible with Aptana that run on Eclipse 3.x API.
If you don't know what to install, there is picture on http://www.nodeclipse.org/updates/
Below is Enide-Recommended-Set-for-Nodejs for example.
(source: nodeclipse.org)
Also look at Enide Studio 2014 http://www.nodeclipse.org/enide/studio/2014/
Here is Enide Studio 2014.17 for win32 with ADT (Android tools) installed,
that I use
If there are still questions, raise issue on https://github.com/nodeclipse/nodeclipse-1/