Render problems android studio

Tek Eye

This article covers several fixes that have solved the Android Studio rendering problems error message that occassionally occurs. Android Studio is Google’s development IDE for Android Apps. Studio is in constant development and as an Android developer you will get used to updating Studio often. Unfortunately the updates will sometimes break existing projects. One of the common errors after an update is an App’s screen failing to display when the layout file is opened in the editor’s Design tab. Instead of the correct screen being shown it is greyed out and overlaid with a Rendering Problems message. Even though the screen displayed correctly before the Studio update. For example the following rendering problems message is saying that there are Missing styles:

Other rendering problem bugs can appear, e.g. Rendering failed with a known bug or The following classes could not be instantiated. Changes in the Android Software Development Kit (SDK) can sometimes affect previously working projects. The project files may need some minor changes to update them to the new SDK.

The Rendering Problems Quick Fix

Sometimes just changing the rendering version (above the Design window) will fix the Rendering Problems error (see the item in the list of fixes). Also opening the the AppTheme dialog, using the AppTheme button (again at the top of the Design window), and clicking OK will fix the rendering problem. If that does not work try reselecting All then AppTheme in the Select Theme dialog. Another quick fix to try is to compile against a previous Android library version. Nearly every SDK update changes the Android libraries and can add beta versions of forthcoming Android releases. Reverting a probject from a beta library to a previous release can sometimes solve a rendering problem, as described in the Different Libraries solution in the following fixes. If these two fixes don’t work try the other fixes below as a solution to any rendering problems message.

List of Possible Fixes for Android Studio Rendering Problems

Here are some solutions to rendering problems in Android Studio. They may not solve you particular issue but have worked in the past, depending upon what has been updated in Studio. These fixes are for when a project was previously compiling and displaying OK in Studio, but after an update the App screens no longer display correctly. These fixes are not guaranteed to work, especially if the code was NOT previously compiling. For previously working code these fixes, or a combination of these solutions, have solved past rendering problems issues.

Change Android Version for Rendering Layouts

Changing the version of Android for rendering layouts can resolve the rendering problems error, especially is beta versions of new Android releases are installed. Use the dropdown above the design area for the opened layout to change the Android version for rendering:

Clean the Project to Fix Rendering Problems

Use the Clean Project menu option under the Build menu in Studio. This occasionally fixes rendering problems.

Update the Studio Cache to Fix Rendering Problems

Rebuilding Studio’s cache can sometimes fix the rendering problems. Close all but one Android project. Use the File menu to select Invalidate Caches/Restart. Confirm the action when the Invalidate Caches message box appears by clicking the Invalidate and Restart button.

Sync Gradle to Fix Rendering Problems

Try resyncing Gradle with the Android project. Use the Sync Project with Gradle Files button on the toolbar. Alternative use the Tools then Android menu option and select Sync Project with Gradle Files.

Update the Project Files to Use Different Library Versions

Check to see if the correct libraries for the project are still installed. For example the v7 appcompat library and associated v4 Support library. First check the SDK directory to see the versions of the libraries available:

Then check the version in the App’s Gradle file (the build.gradle file in the app directory):

Change the version if required, you may be prompted to synch Gradle.

Change an Apps Theme to Fix Rendering Problems

All of the above solutions to layout rendering problems do not change any of the code files for an App. If all the above has been tried and the problems persist further investigation of the error may be needed. Ultimately this could include recreating the App in a new project (copying all the code over) and comparing the new project with the old to determine the issue. (For large projects that may not be a trivial task). Alternatively changing the Apps theme has fixed rendering problems. Use the AppTheme button when viewing a screen in the Design tab to access the available theme definitions. Choose a new theme for an App, e.g. Holo.

See Also

• Rendering Problems with WindowDecorActionBar
• Overview of the Android Support Library
• Styles and Themes on Android Developer

Author: Daniel S. Fowler Published: 2016-05-22 Updated: 2016-06-26

Do you have a question or comment about this article?

(Alternatively, use the email address at the bottom of the web page.)

↓markdown↓ CMS is fast and simple. Build websites quickly and publish easily. For beginner to expert.

Free Android Projects and Samples:

Источник

Android Studio 3.4.1 Render Problem With AppBarLayout #391

Comments

autthapol-k commented Jun 11, 2019

It happened after use
com.google.android.material.appbar.AppBarLayout (lib version: 1.1.0-alpha07)
in xml

The text was updated successfully, but these errors were encountered:

autthapol-k commented Jun 11, 2019 •

got this after force refresh layout

java.lang.IllegalArgumentException: java.lang.ClassCastException@199bfe3d at sun.reflect.GeneratedMethodAccessor1027.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at android.animation.PropertyValuesHolder_Delegate.callMethod(PropertyValuesHolder_Delegate.java:108) at android.animation.PropertyValuesHolder_Delegate.nCallFloatMethod(PropertyValuesHolder_Delegate.java:143) at android.animation.PropertyValuesHolder.nCallFloatMethod(PropertyValuesHolder.java) at android.animation.PropertyValuesHolder.access$400(PropertyValuesHolder.java:38) at android.animation.PropertyValuesHolder$FloatPropertyValuesHolder.setAnimatedValue(PropertyValuesHolder.java:1387) at android.animation.ObjectAnimator.animateValue(ObjectAnimator.java:990) at android.animation.ValueAnimator.setCurrentFraction(ValueAnimator.java:674) at android.animation.ValueAnimator.setCurrentPlayTime(ValueAnimator.java:637) at android.animation.ValueAnimator.start(ValueAnimator.java:1069) at android.animation.ValueAnimator.start(ValueAnimator.java:1088) at android.animation.ObjectAnimator.start(ObjectAnimator.java:852) at android.animation.StateListAnimator.start(StateListAnimator.java:188) at android.animation.StateListAnimator.setState(StateListAnimator.java:181) at android.view.View.drawableStateChanged(View.java:21105) at android.view.ViewGroup.drawableStateChanged(ViewGroup.java:7101) at com.google.android.material.appbar.AppBarLayout.drawableStateChanged(AppBarLayout.java:393) at android.view.View.refreshDrawableState(View.java:21160) at android.view.View.dispatchAttachedToWindow(View.java:18379) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3397) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3404) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3404) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3404) at android.view.AttachInfo_Accessor.setAttachInfo(AttachInfo_Accessor.java:42) at com.android.layoutlib.bridge.impl.RenderSessionImpl.inflate(RenderSessionImpl.java:335) at com.android.layoutlib.bridge.Bridge.createSession(Bridge.java:391) at com.android.tools.idea.layoutlib.LayoutLibrary.createSession(LayoutLibrary.java:195) at com.android.tools.idea.rendering.RenderTask.createRenderSession(RenderTask.java:540) at com.android.tools.idea.rendering.RenderTask.lambda$inflate$5(RenderTask.java:666) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

autthapol-k commented Jun 11, 2019

I guess that the problem from this line, com.google.android.material.appbar.AppBarLayout.drawableStateChanged(AppBarLayout.java:393)

nauhalf commented Jun 11, 2019 •

I got the same problem. I don’t know the problem only appeared in 3.4.1 only or not.

java.lang.IllegalArgumentException: java.lang.ClassCastException@7167546 at sun.reflect.GeneratedMethodAccessor307.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at android.animation.PropertyValuesHolder_Delegate.callMethod(PropertyValuesHolder_Delegate.java:108) at android.animation.PropertyValuesHolder_Delegate.nCallFloatMethod(PropertyValuesHolder_Delegate.java:143) at android.animation.PropertyValuesHolder.nCallFloatMethod(PropertyValuesHolder.java) at android.animation.PropertyValuesHolder.access$400(PropertyValuesHolder.java:38) at android.animation.PropertyValuesHolder$FloatPropertyValuesHolder.setAnimatedValue(PropertyValuesHolder.java:1387) at android.animation.ObjectAnimator.animateValue(ObjectAnimator.java:990) at android.animation.ValueAnimator.animateBasedOnTime(ValueAnimator.java:1339) at android.animation.ValueAnimator.doAnimationFrame(ValueAnimator.java:1471) at android.animation.AnimationHandler.doAnimationFrame(AnimationHandler.java:146) at android.animation.AnimationHandler.access$100(AnimationHandler.java:37) at android.animation.AnimationHandler$1.doFrame(AnimationHandler.java:54) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:947) at android.view.Choreographer.doCallbacks(Choreographer.java:761) at android.view.Choreographer_Delegate.doFrame(Choreographer_Delegate.java:66) at com.android.layoutlib.bridge.impl.RenderSessionImpl.renderAndBuildResult(RenderSessionImpl.java:559) at com.android.layoutlib.bridge.impl.RenderSessionImpl.render(RenderSessionImpl.java:425) at com.android.layoutlib.bridge.BridgeRenderSession.render(BridgeRenderSession.java:120) at com.android.ide.common.rendering.api.RenderSession.render(RenderSession.java:151) at com.android.ide.common.rendering.api.RenderSession.render(RenderSession.java:133) at com.android.tools.idea.rendering.RenderTask.lambda$null$8(RenderTask.java:755) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

If I want to show the preview I must to get rid the AppBarLayout (make the code to be a comment).

Источник

Ошибка рендеринга в Android Studio 3.0 Layout Editor

Я только начал изучать Kotlin для разработки под Android, запустил пустой проект и добавил активность. Я добавил необходимые зависимости gradle, как сказано в документации Kotlin. По умолчанию XML-файл MainActivity содержит только TextView. Но когда я пытаюсь просмотреть XML в Layout Editor, он показывает «Ошибка рендеринга»

Также я получаю это

Я попытался восстановить проект и обновить макет вручную. Но, похоже, ничего не работает.

Так что мне делать? Я использую Android Studio 3.0 Canary 2 с Kotlin

Я добился определенного прогресса. Я обнаружил, что ни одна из моих тем AppCompat не работает.

11 ответов

Хорошо, проверьте ваш gradle, вы добавили поддержку: зависимость appcompat в файле app / build.gradle? также appcompat: зависимость дизайна

Я столкнулся с той же проблемой, когда я пытался автозаполнения. но это будет работать для меня. Убедитесь, что вы добавили эти зависимости:

Если ничего из вышеперечисленного не работает, попробуйте это:

• Перейдите в Инструменты> Android> SDK Manager
• Внутренний внешний вид и поведение> Параметры системы> Android SDK выберите вкладку Инструменты SDK.
• обновите Android SDK Build-Tools до 26.0.1 или более поздней версии.

Этот ответ, скорее всего, решит проблему проблема.

У меня также есть эта проблема, решаемая следующим образом: измените appcompat-v7:26.0.0-beta2 на build.gradle ( modle:app ) на appcompat-v7:26.0.0-beta1 .

Я решил проблему, обновив версию подключаемого модуля gradle до 3.0.0-alpha2 и используя упаковщик gradle gradle-4.0-milestone-1-all.zip.

Я зарегистрировал проблему в трекере проблем андроид-студии — https://issuetracker.google.com/ п / 1 / вопросы / 62251892

Это решение может помочь вам. Изменить style.xml из:

Не удалось выполнить рендеринг в Android Studio android.support.v7.widget.AppCompatImageView

Среда, в которой я работал:
Android Studio 3.0.1

Причина найдена в файле app/build.gradle :

Я изменил некоторые из соответствующих строк следующим образом:

И мне не нужно ничего менять в файле styles.xml . Большинство ответов выше предложили изменить следующую строку:

Я добавил «База». в родительском, чтобы он работал правильно!

Я решил эту проблему, изменив версию дизайна поддержки на ту же версию приложения. Это мой пример зависимости

Ранее я использовал

Есть проблема с версией 25.4.0 поддерживаемых мной библиотек. Я вернулся к версии 25.3.1 и рендер макета работает.

Источник