No clear STR for reproducing this. I have not been able to reproduce this on an emulator with SDK 22 and I only see mainly Huawei and Lenovo devices in the device list. (No such physical device at SV is available for testing ). The stack trace indicates that this is a crash that occurs when the home fragment is displayed and `onMeasure` is called, so no real way to avoid that. Also, no traces as to what Compose component on the main screen is influencing the end result (it might be just the parent layout placing children inside, so again, no way to avoid that ). As the crashes started happening on Compose version upgrade and we do not have the option to downgrade it (it is a requirement for adopting Android 13) I propose we upgrade to 1.3.0. as soon as it is available and follow this signature to see if it still shows up. As a note, I looked into all the release note changes, and none seem to be related to this. Also, I looked into reports of this on the Google issue tracker and there is none. I would have filled one, but with no reproducible sample, it would be ignored. Being isolated to SDK 33 and a few devices would not help prioritize it either.
Bug 1792796 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
No clear STR for reproducing this. I have not been able to reproduce this on an emulator with SDK 22 and I only see mainly Huawei and Lenovo devices in the device list. (No such physical device at SV is available for testing ). The stack trace indicates that this is a crash that occurs when the home fragment is displayed and `onMeasure` is called, so no real way to avoid that. Also, no traces as to what Compose component on the main screen is influencing the end result (it might be just the parent layout placing children inside, so again, no way to avoid that ). As the crashes started happening on Compose version upgrade and we do not have the option to downgrade it (it is a requirement for adopting Android 13) I propose we upgrade to 1.3.0. as soon as it is available (it's already at RC since 5th of October) and follow this signature to see if it still shows up. As a note, I looked into all the release note changes, and none seem to be related to this. Also, I looked into reports of this on the Google issue tracker and there is none. I would have filled one, but with no reproducible sample, it would be ignored. Being isolated to SDK 33 and a few devices would not help prioritize it either.
No clear STR for reproducing this. I have not been able to reproduce this on an emulator with SDK 22 and I only see mainly Huawei and Lenovo devices in the device list. (No such physical device at SV is available for testing ). The stack trace indicates that this is a crash that occurs when the home fragment is displayed and `onMeasure` is called, so no real way to avoid that. Also, no traces as to what Compose component on the main screen is influencing the end result (it might be just the parent layout placing children inside, so again, no way to avoid that ). As the crashes started happening on Compose version upgrade and we do not have the option to downgrade it (it is a requirement for adopting Android 13) I propose we upgrade to 1.3.0. as soon as it is available (it's already at RC since 5th of October) and follow this signature to see if it still shows up. As a note, I looked into all the release note changes, and none seem to be related to this. Also, I looked into reports of this on the Google issue tracker and there is none. I would have filled one, but with no reproducible sample, it would be ignored. Being isolated to SDK 22 and a few devices would not help prioritize it either.