-
Notifications
You must be signed in to change notification settings - Fork 606
Android studio is crashing with this error message after installing this plugin #409
Comments
To get your IDE back and running you have to remove the plugin from this directory "/.AndroidStudio3.2/config/plugins". |
Hi, I am using android studio version 3.1.4. When I am updating Google SceneForm Tools(Beta) plugin from 1.4.0 to 1.5.0, android studio stop working in Windows. I have also try to update Android Studio with the latest version (3.2.0 / 3.2.1) but the same issue occurred android studio stop working. My PC Configuration is as below: Android Studio: 3.1.4 Please help me to resolve this issue. |
Hi,
|
Hi @maraj91 Follow below steps to resolve your issue. Step - 1: Remove your google scene tools (beta) plugin by going to below path in your PC Step - 2: Download Google Scene Form Tools Plugin version 1.4.0 from below link: Google Sceneform Tools (Beta) Step - 3: Install that plugin which you have download from above give link page. To install plugin follow below steps. Restart after installing plugin and enjoy it. |
Hi There is a new update for google scene form tool with version number 1.6.0. And I have tried to update it from version 1.4.0 to 1.6.0. But still, android studio stops working and crash after updating and restart it. Again I try to open the android studio, it did not open. The still crash issue is not resolved. Is anyone get the same issue? |
Couldn't create Engine I am getting above error when open android studio every time. My android studio details are as below:
And in a viewer, I am not able to see the preview of the 3D object which we have created using Google Sceneform Tools for files (sfa and sfb). |
Having same issue when installing Google Sceneform Tools (Beta) (1.7.0) with Android Studio 3.3.1, but it works perfect with 1.4.0 |
That's right we are not able to update it from version 1.4.0 in Windows OS. While I tried it in Mac OS it updated and android studio open after updating it without a crash. |
Im using the plug-in without problems on Windows 10. Never had any crashes - but many other problems 😒 |
But I am getting this issue in Windows 10 as early mention configurations. Android Studio crashed after updating that plugin from version 1.4.0 to latest one. |
Yes there is compatibility issue with latest version of android studio and win 10, when I update plugin to 1.6 or 1.7 even Android Studio wouldn't start. 😒 |
I had to use the plugin today, and it worked as always. Which means its a annoying like hell until it does what it should. But, I don't have crashes. So I wonder, what's different between our environments. I have: |
I have below configuration for my PC.:
|
Hi Is there any solution to resolve the crash issue. Because today I am trying a new thing to resolve the crash issue but it couldn't resolve. Still, android studio crashed. The way I am trying is as below:
I did not crash only when I install 1.4.0 plugin and works fine. Please help me to resolve this issue. And I have also uploaded android studio idea log file in #517 |
@HEMAL-PATEL I'd be happy to help, but I don't know enough about gradle plugins to debug them. My suggestion would be to avoid this plugin, because even when its not crashing, it is very creative in finding all sorts of other trouble. I personally will definitely use gltf models in the future (when materials can finally be created programmatically), which can be imported directly. While this importer also has its problems, there is some interesting work happening for filament, that should make the gltf import work much better (they say). When you need the plugin, I would probably make sure that sceneform and the plugin are the same version. Then I wonder if the project loads with all the sceneform.asset entries removed. Does it crash when adding a certain model as an sceneform.asset, or does it crash with any model? |
hello, yes |
Yes many developers are still getting same issue. Even with latest one version of 1.7.0 or 1.8.0. |
Same issue with Android Studio 3.4.1 and SceneFormPlugin 1.9.0 (beta). Don't know why new versions are being release without this major crash fix. |
That's right @rastogitech Still facing many problems due to this issue. Not be able to use a new feature of this new latest tool. |
Yes am still facing this problem. Using Android Studio 3.4 with Sceneform Plugin 2.9 |
Still crashing. Using Android Studio 3.4.2 with the sceneform plugin 1.10 |
Thats right. Nothing improvement from version 1.5 to 1.10. Android Studio crashed while updating from 1.4 to latest vestion. |
Hi @michaelvogt, Why this issue is not resolved yet. We are unable to check model configurations before running the app. Apart from that every time importing the assets is getting the problem. |
@Satish2804 They even didn't see it necessary to announce some catch-up features as they did so far. |
@michaelvogt Sorry for misunderstanding you as a google developer and Thanks for the info. |
facing same issue. android studio gets close while loading project. |
@chnouman Try to use the latest version of Android Studio with latest version of Sceneform plugin. In my PC that issue is resolved after installing latest version of Android Studio. Before installing the latest version of Android Studio, first of uninstalling Android Studio completely (remove .AndroidStudio3.4 or other files). Android Studio - v3.5 |
@HEMAL-PATEL I resolved this issue by simply removing the project from the path from where the android studio was loading it and placed it on another location. Then tried to open android studio it opened up normally. Again I open a project from a new location and it works. Don't know technical reason behind it. |
@HEMAL-PATEL thank you man you saved my day |
Error Message "Couldn't create Engine"
Couldn't create Engine
java.lang.IllegalStateException: Couldn't create Engine
at com.google.android.filament.Engine.create(Engine.java:37)
at com.google.ar.sceneform.filament.wrapper.Engine.create(Engine.java:14)
at com.google.ar.sceneform.plugin.viewer.Filament$3.run(Filament.java:192)
The text was updated successfully, but these errors were encountered: