-
Notifications
You must be signed in to change notification settings - Fork 600
Sceneform plugin v1.15.0 not working w/Android Studio 3.6 stable (or Android Studio 4 Canary 9) #989
Comments
issue found on Android Studio 3.6 on stabile channel. |
Updated to Androis Studio 3.6 and Sceneform 1.15.0. Every .obj and .fbx import results to: Error: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.android.tools.idea.templates.recipe.RecipeExecutor.append(Ljava/io/File;Ljava/io/File;)
|
Confirm broken w/3.6 stable as well, changing title |
After Android Studio update from stable 3.5.x to 3.6 the Sceneform Import stopped working! Updating tools and gradle versions did not fix this problem... |
Since the plugin is not working anymore, is it possible to import a sceneform asset without android studio? |
@VCDo for now suggest having Android Studio 3.5.3 co-installed and doing all sceneform importing there; after successful import copy all the generated code/files (build.gradle block, .sfa/.sfb/.fbm etc) to your Android Studio 3.6.X or 4.X project and it should work fine -- IIRC using the .sfb isn't the problem, it's just the import process itself that's broken |
Do we have any official confirmation from the Sceneform team as to when this issue will be addressed? |
I have the same issue. |
+1 |
1 similar comment
+1 |
I have the same issue |
IIUC Sceneform v1.16.0 deprecates the entire SceneForm plugin and .sfa/.sfb workflow instead migrating to direct support for .gltf/.glb format assets |
same issue in 3.6.3 |
SceneForm 1.15.0 plugin installed for three versions of Android Studio. Asset imports perfectly in legacy stable Android Studio (3.5.3) but not in
Android Studio 3.5.3
![import_sceneform_asset_android_studio_3 5 3](https://user-images.githubusercontent.com/26958898/74486419-42f26e80-4f00-11ea-84b0-39d3ddb5780c.png)
Android Studio 4 Canary 9
![import_sceneform_asset_android_studio_4_canary_9](https://user-images.githubusercontent.com/26958898/74486257-ea22d600-4eff-11ea-8046-d572fa80d55e.png)
The text was updated successfully, but these errors were encountered: