The new `AndroidSourceDirectorySet` doesn't expose `srcDirs` property [170650362]

Assigned

Bug

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Oct 13, 2020 06:24AM

AGP: 4.1.0

I want to configure Checkstyle tool for all java sources. With older plugin version I was able to call

android.sourceSets.configureEach { sourceSet ->
  val directories: com.android.build.gradle.api.AndroidSourceSet = sourceSet.java.srcDirs
  // then merge `directories` and include all `.java` files
}

Deprecation warning suggests I should use com.android.build.api.dsl.AndroidSourceSet class instead, which doesn't expose srcDirs anymore. If there is another way accessing it it would be nice to have a deprecation warning on the srcDirs property too

Expected result: I'm able to access java srcDirs without Deprecation warning

Actual Result: I able to obtain all java source directories only with a deprecatior warning

Comments

vi...@google.com <vi...@google.com> Oct 13, 2020 07:44AM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Oct 19, 2020 08:17PM

Reassigned to cm...@google.com.

cm...@google.com <cm...@google.com> #2Oct 20, 2020 02:15PM

We have passed this to the development team and will update this issue with more information as it becomes available.

eg...@gmail.com <eg...@gmail.com> #3Oct 21, 2020 07:33PM

This also affects payment apps that start activity from HCE service when user taps the phone on NFC terminal, like our company's Wave2Pay or even your own Google Pay.

zh...@gmail.com <zh...@gmail.com> #4Jul 2, 2021 10:22PM

Please don't harm automation apps, at least allow foreground services : this is affect a lot of app (include mine, Tasker, MacroDroid, ...)
You take down SMS & Call Log permissions, now you take down all entire automation apps.

This will ruin a lot of apps, and developers life...
Please reconsider your decision or propose an alternative !

re...@gmail.com <re...@gmail.com> #5Oct 15, 2022 04:27AM

This affects my accessibility app (Digilux) that lets users launch activities from the accessibility button provided in Android O.

re...@gmail.com <re...@gmail.com> #6Oct 15, 2022 07:13AM

I agree with the author. See also:

https://issuetracker.google.com/issues/128511873

Message last modified on Oct 15, 2022 07:14AM

xa...@google.com <xa...@google.com> #7Dec 28, 2022 06:14PM

Google should be supporting and encouraging automation app developers and users, not limiting us!

ma...@gmail.com <ma...@gmail.com> #8Jan 24, 2023 08:25PM

Agree. We have a remote control automation app but the user is always in control of the launch of activities from the remote. Can Google not consider allowing the user to enable/disable this from the security tab and or insist that a foreground service with a persistent notification is exempt?

xa...@google.com <xa...@google.com> #9Jan 24, 2023 08:36PM

Once again, thank you for submitting the feature request. After following up with our product and engineering teams, the feature request will not be considered at this time.
Note that the final Android 10 release incorporated several exceptions to when activity starts are allowed from the background - see here:

https://developer.android.com/guide/components/activities/background-starts#exceptions

ma...@gmail.com <ma...@gmail.com> #10Jan 24, 2023 09:23PM

@9 What about backward compatibility?

Why not present a new permission that will ask the user if it's ok for this app to open the Activity in the background?
This way you can still avoid breaking apps, while letting the user know about it.