Search Issue Tracker
Fixed in 2018.1
Fixed in 2018.2
Votes
0
Found in
2018.1.0f2
Issue ID
1038644
Regression
Yes
[Android] $applicationId tag in a manifest causes Gradle build to fail
Steps to reproduce:
1. Open user attached project
2. Build for Gradle
3. Observe that build fails
Expected result: $applicationId tag in a manifest should not cause Gradle build to fail
Reproduced in: 2018.3.0a1, 2018.2.0b5, 2018.1.0f2, 2018.1.0b1
Not reproduced in: 2018.1.0a7, 2017.4.3f1, 2017.3.2f1
Regressions since: 2018.1.0b1
Fixed in: 2018.3.0a3
Backported to: 2018.2.0b10, 2018.1.7f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [VCS] Improve UI/UX of connection params (history of previous params, auto-find p4config, etc.)
- [VCS] After working offline in Perforce, show UI for "p4 reconcile" or some other way of getting in sync
- [VCS] UI lacks a File History window (note: needs plugin changes, UI work)
- [VCS] Version Control window context menu: add "Open in P4V" and tweak wording
- [VCS] Perforce/etc. settings could really use a separate entry in Project Settings sidebar
Add comment