Layout rendering inside AS stops on most of layout after upgrade to 2021.3.1 RC 1 (worked on Chipmunk) [247544242]

Duplicate

of 247058594

Bug

Status Update

No update yet.

Description

to...@gmail.com

created issue #1

Sep 19, 2022 04:07PM

After upgrading to Dolphin from Chipmunk many layouts in our app stopped rendering. It is still working on some demo apps, but not in our app.

It always ending on something missing like

android.content.res.Resources$NotFoundException: Could not find styleable resource matching value 0x0 (resolved name: Window_backgroundDimAmount) in current configuration. Or the resolved value was not of type layout as expected.
	at android.content.res.Resources_Delegate.throwException(Resources_Delegate.java:1161)
	at android.content.res.Resources_Delegate.throwException(Resources_Delegate.java:1137)
	at android.content.res.Resources_Delegate.getLayout(Resources_Delegate.java:503)
	at android.content.res.Resources.getLayout(Resources.java:1252)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:536)
	at com.avast.android.cleaner.databinding.ViewDataSectionBinding.inflate(ViewDataSectionBinding.java:59)
	at com.avast.android.cleaner.view.DataSectionView.<init>(DataSectionView.kt:30)
	at com.avast.android.cleaner.view.DataSectionView.<init>(DataSectionView.kt:24)
	at com.avast.android.cleaner.view.DataSectionView.<init>(DataSectionView.kt)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at org.jetbrains.android.uipreview.ViewLoader.createNewInstance(ViewLoader.java:351)
	at org.jetbrains.android.uipreview.ViewLoader.loadClass(ViewLoader.java:200)
	at org.jetbrains.android.uipreview.ViewLoader.loadView(ViewLoader.java:161)
	at com.android.tools.idea.rendering.LayoutlibCallbackImpl.loadView(LayoutlibCallbackImpl.java:294)
	at android.view.BridgeInflater.loadCustomView(BridgeInflater.java:417)
	at android.view.BridgeInflater.loadCustomView(BridgeInflater.java:428)
	at android.view.BridgeInflater.createViewFromTag(BridgeInflater.java:332)
	at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:965)
	at android.view.LayoutInflater.rInflate_Original(LayoutInflater.java:1127)
	at android.view.LayoutInflater_Delegate.rInflate(LayoutInflater_Delegate.java:72)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:1101)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1088)
	at android.view.LayoutInflater.rInflate_Original(LayoutInflater.java:1130)
	at android.view.LayoutInflater_Delegate.rInflate(LayoutInflater_Delegate.java:72)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:1101)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1088)
	at android.view.LayoutInflater.rInflate_Original(LayoutInflater.java:1130)
	at android.view.LayoutInflater_Delegate.rInflate(LayoutInflater_Delegate.java:72)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:1101)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1088)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:686)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:505)
	at com.android.layoutlib.bridge.impl.RenderSessionImpl.inflate(RenderSessionImpl.java:359)
	at com.android.layoutlib.bridge.Bridge.createSession(Bridge.java:436)
	at com.android.tools.idea.layoutlib.LayoutLibrary.createSession(LayoutLibrary.java:121)
	at com.android.tools.idea.rendering.RenderTask.createRenderSession(RenderTask.java:717)
	at com.android.tools.idea.rendering.RenderTask.lambda$inflate$9(RenderTask.java:873)
	at com.android.tools.idea.rendering.RenderExecutor$runAsyncActionWithTimeout$3.run(RenderExecutor.kt:192)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

Another stacktrace is in another-stacktrace.png

Project themes are all correctly displayed in the theme selector.

Build: AI-213.7172.25.2113.8913347, 202208060259,

AI-213.7172.25.2113.8913347, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 2560.0x1440.0, 2560.0x1440.0

AS: Dolphin | 2021.3.1 RC 1 Kotlin plugin: 213-1.7.10-release-for-android-studio-AS6777.52 Android Gradle Plugin: 7.3.0-rc01 Gradle: 7.5.1 Gradle JDK: Eclipse Temurin version 17.0.3

Snímek obrazovky 2022-09-19 174812.png

44 KB

View

Download

idea.log

98 KB

View

Download

another-stacktrace.png

137 KB

View

Download

Comments

to...@gmail.com <to...@gmail.com> #2Sep 19, 2022 04:50PM

Automated by Blunderbuss job edu-devrel-blunderbuss-autoassigner for component 191645.

ra...@google.com <ra...@google.com> Sep 19, 2022 08:19PM

Status: Duplicate of

247058594

so...@google.com <so...@google.com> #3Sep 21, 2022 10:40PM

Assigned to cm...@google.com.

Upon some more investigation, I've noticed that Excusing a submission via the UI simply removes it from calculation of overall grade within the UI. However, the actual score of the submission does not change -- in my original case reported above, the original score I gave to the submission was 0, and then I marked it as Excused.

In my opinion, at least one of the two should change with regards to the behavior of Excusing an assignment:

1. Any original score returned to the student should be erased from the submission entirely. This should make the returned grade empty/null, so the API response does not need any special indicator for an excused grade.
2. If a returned grade should still be associated with a submission (but not count towards the overall grade like the Google Classroom UI calculates), then this same flag/indicator should be exposed via the API so that a similar overall grade calculation can be performed from the API response.

to...@gmail.com <to...@gmail.com> #4Sep 22, 2022 06:22AM

Thanks for providing feedback around supporting excused assignments in the Classroom API! I've made a note of your comments and transferred them internally. Any updates about this will be communicated here.

cm...@google.com <cm...@google.com> #5Sep 22, 2022 09:29AM

Status: Duplicate of

247058594

We are an SIS that consumes Classroom data via the API.

What we are observing:

we don't get StudentSubmissions where student was never scored and was excused, so parents are confused thinking that work is not done when it should be excused when looking in our platform.
When a student is scored, grades are synced, then excused, we don't get the update that the assignment was excused. So now the student has a score (0 or otherwise) that doesn't reflect what's in Google Classroom, creating discrepancies between Classroom assignment grades and SIS assignment grades.

to...@gmail.com <to...@gmail.com> #6Sep 22, 2022 10:41AM

Thanks for providing supporting feedback. I'd love to learn a bit more about your comment:

"we don't get StudentSubmissions where student was never scored and was excused, so parents are confused thinking that work is not done when it should be excused when looking in our platform."

Can you provide more information on the API call you are making here so I can try to figure out the issue? I'm not able to reproduce this at the moment; when reading student submissions by calling ListStudentSubmissions, I'm able to retrieve submissions that are marked as excused in the UI.

"When a student is scored, grades are synced, then excused, we don't get the update that the assignment was excused. So now the student has a score (0 or otherwise) that doesn't reflect what's in Google Classroom, creating discrepancies between Classroom assignment grades and SIS assignment grades."

Trying to understand this issue a bit further - if I understand correctly, there may be grade discrepancies between Classroom and SIS in the event that a teacher modifies a grade after the grades have been synced with the SIS. Do you have a mechanism today by which you monitor these types of grade changes? If not, is being alerted about excused assignments more important than other types of submission changes?

Issue 247544242

Description

Issue summary

Comments

to...@gmail.com <to...@gmail.com> #2Sep 19, 2022 04:50PM

ra...@google.com <ra...@google.com> Sep 19, 2022 08:19PM

so...@google.com <so...@google.com> #3Sep 21, 2022 10:40PM

to...@gmail.com <to...@gmail.com> #4Sep 22, 2022 06:22AM

cm...@google.com <cm...@google.com> #5Sep 22, 2022 09:29AM

to...@gmail.com <to...@gmail.com> #6Sep 22, 2022 10:41AM

Add comment

Issue metadata