

Ideally don't port everything all at once and use something like Git to keep track of changes. It'll be a pain but might be easier than trying to figure out what is broken in the old code. If that's the case you could try to port the code into the new project. If you have a project that works, try to see if any src, res or build directories are missing.Īlternatively, you could try to create a new empty project in Android Studio, see if that builds. "res") and that was causing build issues. I've also had issues where a previously empty directory was missing (e.g. Try to check if the permissions are set correctly, as said. The project may be using outdated configuration that no longer works on the latest version of Android Studio/Gradle. The project was copied as one whole project over a USB Drive, however I forget to mention that the Android studio version on the previous machine was outdated and on the current machine it is updated.
