IssueTracker

Component used: watchface-complications-data-source-ktx

Version used: 1.3.0-alpha04, 1.2.1

Devices/Android versions reproduced on: Samsung Galaxy Watch 5/Wear OS 5.0/Android 14

When an activity start PendingIntent is specified as the tap action in a complication, on Wear OS 5/Android 14 the activity start is blocked. This basically makes the tap action do nothing.

The problem does not appear with non-timeline complications or when the fallback ComplicationData is used.

When running on Wear OS emulator (SDK 34 image), this is printed in the logs when the complication is tapped:

 With Android 14 BAL hardening this activity start will be blocked if the PI sender upgrades target_sdk to 34+!  (missing opt in by PI sender)![callingPackage: com.lkoskela.complicationtaptest; callingPackageTargetSdk: 34; callingUid: 10115; callingPid: -1; appSwitchState: 2; callingUidHasAnyVisibleWindow: false; callingUidProcState: CACHED_RECENT; isCallingUidPersistentSystemProcess: false; forcedBalByPiSender: BSP.NONE; intent: Intent { cmp=com.lkoskela.complicationtaptest/.presentation.MainActivity }; callerApp: null; balAllowedByPiCreator: BSP.ALLOW_BAL; balAllowedByPiCreatorWithHardening: BSP.ALLOW_BAL; resultIfPiCreatorAllowsBal: BAL_BLOCK; hasRealCaller: true; isCallForResult: false; isPendingIntent: true; autoOptInReason: null; realCallingPackage: com.google.android.wearable.watchface.rwf; realCallingPackageTargetSdk: 33; realCallingUid: 10068; realCallingPid: 884; realCallingUidHasAnyVisibleWindow: true; realCallingUidProcState: BOUND_FOREGROUND_SERVICE; isRealCallingUidPersistentSystemProcess: false; originatingPendingIntent: PendingIntentRecord{de42ffa com.lkoskela.complicationtaptest startActivity}; realCallerApp: ProcessRecord{6997c8f 884:com.google.android.wearable.watchface.rwf/u0a68}; realInVisibleTask: false; balAllowedByPiSender: BSP.ALLOW_BAL; resultIfPiSenderAllowsBal: BAL_ALLOW_VISIBLE_WINDOW]

On my Galaxy Watch 5 similar logs are printed ("Without BAL hardening this would be allowed...") but the activity launch is actually blocked.

Sample project: https://github.com/luryus/complication-tap-test/

This simple sample code exhibits the problem:

    override fun onComplicationRequest(
        request: ComplicationRequest,
        listener: ComplicationRequestListener
    ) {
        val timelineEntries = listOf(
            TimelineEntry(
                TimeInterval(
                    Instant.now().minusSeconds(3600),
                    Instant.now().plusSeconds(3600)
                ), createComplicationData()
            )
        )
        val timeline = ComplicationDataTimeline(
            createComplicationData(), timelineEntries
        )
        listener.onComplicationDataTimeline(timeline)
    }

    private fun createComplicationData(): ComplicationData {
        val pi = PendingIntent.getActivity(
            this,
            0,
            Intent(this, MainActivity::class.java),
            PendingIntent.FLAG_IMMUTABLE or PendingIntent.FLAG_UPDATE_CURRENT
        )
        return ShortTextComplicationData.Builder(
            text = PlainComplicationText.Builder("foo").build(),
            contentDescription = PlainComplicationText.Builder("foo").build()
        ).setTapAction(pi).build()
    }

Changing the timeline creation to this makes the tap action work but of course prevents using the timeline feature:

        val timeline = ComplicationDataTimeline(
            createComplicationData(), emptyList()
        )

Is there any workaround from the app side for this, if using complication timelines is critical for the complication's use case (precise data update timing is required)?