Not sure if anyone else uses <fastlane> to automat...
# compose-wear
y
Not sure if anyone else uses fastlane to automate play store releases, but if you do this screenshot strategy, fixes the screenshots to be acceptable for the Play Store https://github.com/yschimke/rememberwear/blob/main/wear/src/androidTest/kotlin/com/google/wear/soyted/fastlane/WearScreenshotStrategy.kt
Copy code
private fun screenshot(screenshotName: String, block: @Composable () -> Unit) {
        composeTestRule.setContent {
            RememberTheMilkTheme {
                Scaffold(timeText = {
                    TimeText(timeSource = FixedTimeSource)
                }) {
                    block()
                }
            }
        }

        composeTestRule.onRoot().assertIsDisplayed()

        val context = InstrumentationRegistry.getInstrumentation().context
        val isScreenRound = context.resources.configuration.isScreenRound
        Screengrab.screenshot(screenshotName, WearScreenshotStrategy(isRoundDevice = isScreenRound))
    }
t
Thank you for sharing this! My screenshots keep getting rejected by Google and I have been stuck on this for weeks now. Their policy team is not helpful at all and don’t want to explain the issue in detail. I will try out your solution and hope that solves it. I really hope that filling the background with a solid colour will help, even though the screenshot was taken directly from an official Wear OS emulator.
y
@Thomas I think this will be fixed in the tooling eventually, but until that happens, did you get past this?
t
Yes, the update was approved. Thank you so much!
It does look like there is a small border still visible, but it is not that big of an issue. I am already glad I can update my app again.
message has been deleted