Infeasible
Status Update
Comments
ba...@google.com <ba...@google.com> #2
Can you confirm if this is a regression compared to a previous version you were using?
ba...@google.com <ba...@google.com> #3
Please provide info on the device model and API level used to reproduce the bug.
Running the sample above (with surface) at tip of tree on a pixel 7 device, I am able to observe the text change and button's ripple effect.
im...@gmail.com <im...@gmail.com> #4
I have attached a reproducer project. I think the key point is to also wrap RootContent
with Surface {}
.
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
enableEdgeToEdge()
setContent {
Surface {
RootContent()
}
}
}
}
sa...@gmail.com <sa...@gmail.com> #5
Reproducible on an API 34 emulator.
Properties
avd.ini.displayname Pixel 7 API 34
avd.ini.encoding UTF-8
AvdId Pixel_7_API_34
disk.dataPartition.size 6442450944
fastboot.chosenSnapshotFile
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot yes
fastboot.forceFastBoot no
hw.accelerometer yes
hw.arc false
hw.audioInput yes
hw.battery yes
hw.camera.back virtualscene
hw.camera.front emulated
hw.cpu.ncore 4
hw.device.hash2 MD5:3db3250dab5d0d93b29353040181c7e9
hw.device.manufacturer Google
hw.device.name pixel_7
hw.dPad no
hw.gps yes
hw.gpu.enabled yes
hw.gpu.mode auto
hw.initialOrientation Portrait
hw.keyboard yes
hw.lcd.density 420
hw.lcd.height 2400
hw.lcd.width 1080
hw.mainKeys no
hw.ramSize 2048
hw.sdCard yes
hw.sensors.orientation yes
hw.sensors.proximity yes
hw.trackBall no
image.androidVersion.api 34
image.sysdir.1 system-images/android-34/google_apis_playstore/arm64-v8a/
PlayStore.enabled true
runtime.network.latency none
runtime.network.speed full
showDeviceFrame yes
skin.dynamic yes
tag.display Google Play
tag.id google_apis_playstore
tag.ids google_apis_playstore
vm.heapSize 228
ar...@gmail.com <ar...@gmail.com> #6
It's also reproducible with Compose 1.8.0-alpha05
and M3 1.2.0
. Not reproducible with Compose 1.8.0-alpha04
and M3 1.2.0
. Looks like the regression was introduced in Compose 1.8.0-alpha05
.
ia...@gmail.com <ia...@gmail.com> #7
Comment has been deleted.
ia...@gmail.com <ia...@gmail.com> #8
The issue seems specifically related to ReusableContent and layers (SaveableStateProvider uses ReusableContent internally), I guess we made some assumptions that don't work in the reuse case
Description
Deployment to app engine flex environment fails with following message:
where *** is the project Id
Note the command is run from the google Cloud Build step using command
The google build service has following roles assigned:
The same deployment worked without issues last week. Only change from our side was switching the repository for the build trigger.
There is related question on Stack Overflow:https://stackoverflow.com/questions/64236468/cloud-build-fails-to-deploy-to-google-app-engine-you-do-not-have-permission-to which indicates the issue started to manifest recently.