Skip to content

[quick_actions] Flaky failure in appShortcutLaunchActivityAfterStarting #110022

@stuartmorgan-g

Description

@stuartmorgan-g

Android failed appShortcutLaunchActivityAfterStarting, but passed on a re-run.

java.lang.AssertionError: AppShortcut:action_one does not launch the correct activity
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at io.flutter.plugins.quickactionsexample.QuickActionsTest.appShortcutLaunchActivityAfterStarting(QuickActionsTest.java:114)
at java.lang.reflect.Method.invoke(Native Method)

The video does show that the title has updated to "action_one has launched", so it's not clear why the assertion failed; it suggests that there's a problem in the test assertions rather than the plugin functionality. This test is only about a month old, which also points to a test issue rather than a regression.

This failed both devices on the first run, only one device on the auto-rerun, and then passed when the task was manually re-run. So it's potentially quite flaky.

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.c: flakeTests that sometimes, but not always, incorrectly passp: quick_actionsQuickActions pluginpackageflutter/packages repository. See also p: labels.platform-androidAndroid applications specifically

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions