Open
Description
What feature would you like to see?
At the moment there are four exceptions when you enable org.gradle.unsafe.isolated-projects=true
, all pointing at the usage of findProperty
to retrieve these properties:
- com.google.firebase.crashlytics.buildtools
- com.google.firebase.crashlytics.fakeId
- com.google.firebase.crashlytics.fakeOutput
- com.google.firebase.crashlytics.logDebug
I believe these can be changed to providers.gradleProperty(...)
to solve the issue.
How would you use it?
Isolated projects would improve performance of the "sync" step in Android Studio:
https://docs.gradle.org/current/userguide/isolated_projects.html
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
google-oss-bot commentedon Mar 8, 2025
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
[-]Support Gradle Isolated Projects[/-][+]Gradle Plugin: support Gradle isolated projects[/+]mrober commentedon Mar 14, 2025
Thanks for reporting this @cymerio. Those properties are for our automated tests only. I didn't realize they were violating project isolation. I will find another way to set up the tests.
liutikas commentedon Mar 18, 2025
You don't need to remove these, you just need to move from findProperty to providers.gradleProperty as noted in the OP.
The issue is that findProperty is recursive and calls to all parent projects, causing the IP violation.
liutikas commentedon Mar 18, 2025
Similar issues are there in FirebasePerfPlugin
and