ADT 22.3 (android 4.4) - getting error "After scene creation, #init() must be called"

Asked 3/11, 2013 at 8:33 Answered 27/11, 2013 at 10:33

Solved android eclipse adt gui-designer android-4.4-kitkat

After installing the new ADT (22.3.0.v201310242005-887826) which supports Android 4.4 (KitKat), I keep getting the error as shown here:

Enter image description here

An internal error has occurred

In the list of errors, I see multiple items of "RenderPreview", and when I click on any of them, I see:

An internal error has occurred. After scene creation, #init() must be called

When testing the new ADT on another computer, I can't see this error appearing there. This is very weird.

Why do I get those errors, and what can I do to fix it?

Coincident answered 3/11, 2013 at 8:33 Comment(7)

I have the same problems. – Hagiocracy 3/11, 2013 at 11:46

@Hagiocracy that's good. it means I didn't do anything wrong (this time :) ) – Coincident 3/11, 2013 at 12:44

Exactly the same problem, I just also opened a question myself. Didn't see your question before. – Obstructionist 3/11, 2013 at 20:53

I also using Scene class in my project(for starting transtion) but min API version 19 but I want to support under 19 how can I change this ? – Alexipharmic 20/11, 2014 at 6:57

@ZaferCelaloglu I don't know about Scene class, but in order to support lower APIs, you need to set "minSdkVersion" in the manifest. the "targetSdkVersion" should be set to the max available (which is 21 currently) . I suggest reading the documentation: developer.android.com/guide/topics/manifest/… – Coincident 20/11, 2014 at 7:54

yeah I know this but function doesnt working under 19 API. – Alexipharmic 20/11, 2014 at 10:48

@ZaferCelaloglu Which function is it that you are trying to use? there are many classes/functions that can overcome this inside the support library and third party libraries. If there isn't, you can always perform a check: "if(VERSION.SDK_INT>=VERSION_CODES.KITKAT)..." . – Coincident 20/11, 2014 at 15:31

I've created a bug report. Until it gets fixed, set the API version in the UI preview to something lower than 19. The error only shows up for version 19.

Qr answered 5/11, 2013 at 18:18 Comment(5)

what's weird is that on some computers it doesn't occur. – Coincident 5/11, 2013 at 21:56

FYI: the bug status got set to "fixed", so i guess it will be part of the next ADT update. – Qr 25/11, 2013 at 18:5

ah, thank you for your answer. Today, got this error after update into kitkat... weird – Birkenhead 15/12, 2013 at 11:58

seems that this bug was fixed. i've updated the SDK (to 22.3? i'm not sure) and now it works fine. – Coincident 22/12, 2013 at 13:30

Yes, confirmed. The latest SDK update fixes the problem. – Qr 30/12, 2013 at 19:19

I have the same experience, but one downgrade to Android 4.3 (Jelly Bean) is for me now only the successful temporary solution.

Serotine answered 3/11, 2013 at 23:46 Comment(1)

Sadly, the same computer also has another issue (with custom views) on the UI designer, no matter which ADT it has. I've reported about it here: #18120407 – Coincident 4/11, 2013 at 6:28

Just scroll down from API 19 to API 18, The Android Image in the Graphical Layout.

Colwin answered 15/11, 2013 at 23:44 Comment(0)

Temporary solution until Google fixes it:

Workaround: Switch to Android-18 in Graphical Layout (green Android top-right).

Reference: Stack Overflow question How to fix Eclipse ADT Plugin 22.3 / SDK Tools 22.3 with broken properties window?

Peggy answered 9/11, 2013 at 7:35 Comment(0)

After installing the new ADT (22.3.0.v201310242005-887826) which supports Android 4.4 (kitkat), I got the same error.

Then set the API version in the UI preview to something lower than 19. The error only shows up for version 19.

Enter image description here

Textuary answered 27/11, 2013 at 10:33 Comment(0)

In my view, it is a new bug. May be we need to wait for Google to update it.

Deb answered 5/11, 2013 at 8:53 Comment(0)

Recommended topics

Hot tags