4

Android studio is a fucking demon that clings to your projects' soul.

>> Was working on project "a"
>> Thought of doing something different, but didn't wanted to create a whole new project or integrate changes here, so simply copied the project in a new folder "a_copy".(even copied the cache for faster build)

EXPECTATIONS :
1) i will be simply working on a copy of the project.
2)every changes made in a_copy will remain in a_copy.
3) when trying to build and run , my old app will be updated with new changes.
4) And if those changes doesn't fit, i will be simply removing a_copy files, going back to unaltered project "a" .
5) Building and running project "a" will update my previously updated app back to old state

REALITY :
1) ANY CHANGES MADE INTO PROJECT a_copy ARE REFLECTED BACK TO PROJECT "a" ! EVEN WHEN PROJECT "a_copy" IS CLOSED!
2) NO CHANGES OCCUR IN "a_copy", it remains in the same state as that of "a_copy", before all those changes got reflected!!

WHAT THE ACTUAL FUCK? its like studio treated the whole project copy as some windows shortcut?!?!

Comments
  • 3
    could it be that the project contains hardcoded absolute paths to ur files? try to rename ‚a‘ and see if ‚a_copy‘ still opens and works ... i guess not
Add Comment