IssueTracker

We're seeing a similar error in our code. Appears to be a combination of AGP 8.6.0 and Kotlin 2 needed to hit it.

private fun Intent.stripUnwantedFlags() {
    // Explicitly remove the new task and clear task flags (Our browser activity is a single
    // task activity and we never want to start a second task here).
    flags = flags and Intent.FLAG_ACTIVITY_NEW_TASK.inv()
    flags = flags and Intent.FLAG_ACTIVITY_CLEAR_TASK.inv()

    // IntentReceiverActivity is started with the "excludeFromRecents" flag (set in manifest). We
    // do not want to propagate this flag from the intent receiver activity to the browser.
    flags = flags and Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS.inv()
}

All 3 lines then hit:

Must be one or more of: Intent.FLAG_GRANT_READ_URI_PERMISSION, Intent.FLAG_GRANT_WRITE_URI_PERMISSION, Intent.FLAG_FROM_BACKGROUND, Intent.FLAG_DEBUG_LOG_RESOLUTION, Intent.FLAG_EXCLUDE_STOPPED_PACKAGES, Intent.FLAG_INCLUDE_STOPPED_PACKAGES, Intent.FLAG_GRANT_PERSISTABLE_URI_PERMISSION, Intent.FLAG_GRANT_PREFIX_URI_PERMISSION, Intent.FLAG_ACTIVITY_MATCH_EXTERNAL, Intent.FLAG_ACTIVITY_NO_HISTORY, Intent.FLAG_ACTIVITY_SINGLE_TOP, Intent.FLAG_ACTIVITY_NEW_TASK, Intent.FLAG_ACTIVITY_MULTIPLE_TASK, Intent.FLAG_ACTIVITY_CLEAR_TOP, Intent.FLAG_ACTIVITY_FORWARD_RESULT, Intent.FLAG_ACTIVITY_PREVIOUS_IS_TOP, Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS, Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT, Intent.FLAG_ACTIVITY_RESET_TASK_IF_NEEDED, Intent.FLAG_ACTIVITY_LAUNCHED_FROM_HISTORY, Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET, Intent.FLAG_ACTIVITY_NEW_DOCUMENT, Intent.FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET, Intent.FLAG_ACTIVITY_NO_USER_ACTION, Intent.FLAG_ACTIVITY_REORDER_TO_FRONT, Intent.FLAG_ACTIVITY_NO_ANIMATION, Intent.FLAG_ACTIVITY_CLEAR_TASK, Intent.FLAG_ACTIVITY_TASK_ON_HOME, Intent.FLAG_ACTIVITY_RETAIN_IN_RECENTS, Intent.FLAG_ACTIVITY_LAUNCH_ADJACENT, Intent.FLAG_ACTIVITY_REQUIRE_NON_BROWSER, Intent.FLAG_ACTIVITY_REQUIRE_DEFAULT, Intent.FLAG_RECEIVER_REGISTERED_ONLY, Intent.FLAG_RECEIVER_REPLACE_PENDING, Intent.FLAG_RECEIVER_FOREGROUND, Intent.FLAG_RECEIVER_NO_ABORT, Intent.FLAG_RECEIVER_VISIBLE_TO_INSTANT_APPS

The initial report (comment#1) seems like a dup of b/352609562 (internal link), and fixed at https://cs.android.com/android-studio/platform/tools/base/+/f88d11033727f891bcc2a7a1cbbeb109c7d5dd0f I believe it's available in AGP 8.7.0-alpha02+

However, comment#2 indicates that there are more kinds of conversions we may miss... Let me double-check that.

Thanks for fixing! What release should we be able to verify the fix in? And is there any chance of a backport for 8.6.1?

The caveat is that the fix for comment#1 is in 8.7.0-alpha02 and the fix for comment#2 will be in 8.8.0-alpha02. I'm asking internally how we can handle this case.

the fix for comment#2 will be in 8.8.0-alpha02

It is cherry-picked to 8.7

the fix for comment#1 is in 8.7.0-alpha02

This one and the above one are cherry-picked to 8.6.1

Thanks for the update!

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
• Android Gradle Plugin 8.8.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

The fixes for this issue are now also available in:

• Android Studio Ladybug | 2024.2.1 RC 1
• Android Gradle Plugin 8.7.0-rc01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thanks, I will investigate why the fix seems to have disappeared from Ladybug Feature Drop.

The fixes for this issue are now also available in:

• Android Studio Meerkat Feature Drop | 2024.3.2 Canary 2
• Android Gradle Plugin 8.10.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

To update you on this:

I took a deeper look at the implementation of the change detector, and the banner displayer, and discovered a bit of a rats' nest. I've merged some fixes into our latest canary (as suggested by the above comment) and have also booked a meeting with owners to discuss ideas around redesigning / changing its implementation completely in order to make it more robust.

This bug might get more automated release notifications of the above kind as we make progress. Thanks once again.

Further fixes for this issue are now available in:

• Android Studio Meerkat Feature Drop | 2024.3.2 Canary 3
• Android Gradle Plugin 8.10.0-alpha03

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.