Sceneform-android-sdk: Sceneform plugin v1.15.0 not working w/Android Studio 3.6 stable (or Android Studio 4 Canary 9)

Created on 14 Feb 2020 · 13Comments · Source: google-ar/sceneform-android-sdk

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

latest stable (3.6)
latest preview (4 canary 9)

Android Studio 3.5.3
import_sceneform_asset_android_studio_3 5 3

Android Studio 4 Canary 9
import_sceneform_asset_android_studio_4_canary_9

Source

tellypresence

👍3

Most helpful comment

issue found on Android Studio 3.6 on stabile channel.
import .obj file result in Error: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.android.tools.idea.templates.recipe.RecipeExecutor.append(Ljava/io/File;Ljava/io/File;)

AndreaGrizzi on 20 Feb 2020

👍10

All 13 comments

AndreaGrizzi on 20 Feb 2020

👍10

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;)

Tried to re-install sceneform -> no effect

dawcules on 27 Feb 2020

👍4

Confirm broken w/3.6 stable as well, changing title

tellypresence on 28 Feb 2020

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...

VCDo on 28 Feb 2020

Since the plugin is not working anymore, is it possible to import a sceneform asset without android studio?

VCDo on 2 Mar 2020

@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
...or just hold back on 3.5.3 pending proper fix...

tellypresence on 3 Mar 2020

Do we have any official confirmation from the Sceneform team as to when this issue will be addressed?