After migrating old Android project to Gradle, R is unknown
I have migrated an old (2013) Java Android project to use Gradle as per the instructions in https://developer.android.com/studio/intro/migrate.
I have used the "Migrate by creating a new empty project strategy", the other strategy is "Migrate by creating a custom Gradle build file" but I have used the first.
After following the steps, I build my app in Android Studio and get the error "package R does not exist" in the Java files that use R.
I see that no gen directory is generated when building, so no wonder the R class is unknown.
Any ideas I might try? Thanks a lot.
android 
android-gradle migrate asked Nov 28 '18 at 23:04
PavitxPavitx
42112
add a comment |
I have migrated an old (2013) Java Android project to use Gradle as per the instructions in https://developer.android.com/studio/intro/migrate.
I have used the "Migrate by creating a new empty project strategy", the other strategy is "Migrate by creating a custom Gradle build file" but I have used the first.
After following the steps, I build my app in Android Studio and get the error "package R does not exist" in the Java files that use R.
I see that no gen directory is generated when building, so no wonder the R class is unknown.
Any ideas I might try? Thanks a lot.
android android-gradle migrate asked Nov 28 '18 at 23:04
PavitxPavitx
42112
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12
add a comment |
I have migrated an old (2013) Java Android project to use Gradle as per the instructions in https://developer.android.com/studio/intro/migrate.
I have used the "Migrate by creating a new empty project strategy", the other strategy is "Migrate by creating a custom Gradle build file" but I have used the first.
After following the steps, I build my app in Android Studio and get the error "package R does not exist" in the Java files that use R.
I see that no gen directory is generated when building, so no wonder the R class is unknown.
Any ideas I might try? Thanks a lot.
android android-gradle migrate asked Nov 28 '18 at 23:04
PavitxPavitx
42112
I have migrated an old (2013) Java Android project to use Gradle as per the instructions in https://developer.android.com/studio/intro/migrate.
I have used the "Migrate by creating a new empty project strategy", the other strategy is "Migrate by creating a custom Gradle build file" but I have used the first.
After following the steps, I build my app in Android Studio and get the error "package R does not exist" in the Java files that use R.
I see that no gen directory is generated when building, so no wonder the R class is unknown.
Any ideas I might try? Thanks a lot.
android android-gradle migrate android android-gradle migrate asked Nov 28 '18 at 23:04
PavitxPavitx
42112
asked Nov 28 '18 at 23:04
PavitxPavitx
42112
asked Nov 28 '18 at 23:04
PavitxPavitx
42112
asked Nov 28 '18 at 23:04
PavitxPavitx
42112
asked Nov 28 '18 at 23:04
PavitxPavitx
42112
42112
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12
add a comment |
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12
add a comment |
1 Answer
1
active
oldest
votes
Since I was using the method "Migrate by creating a new empty project strategy" I created a directory and application named myprojectgradle and the package generated was com.example.myprojectgradle where my previous package was com.example.myproject. I fixed the package but the -gradle suffix was present in some places and confusing Android Studio.
I changed the package in the generated unit test files (not important and are just boilerplate) and also removed the -gradle suffix in the build.gradle file applicationId property.
Probably when you are using that strategy you should name your new project with the same name as the old non-Gradle project and keep the same package.
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529431%2fafter-migrating-old-android-project-to-gradle-r-is-unknown%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since I was using the method "Migrate by creating a new empty project strategy" I created a directory and application named myprojectgradle and the package generated was com.example.myprojectgradle where my previous package was com.example.myproject. I fixed the package but the -gradle suffix was present in some places and confusing Android Studio.
I changed the package in the generated unit test files (not important and are just boilerplate) and also removed the -gradle suffix in the build.gradle file applicationId property.
Probably when you are using that strategy you should name your new project with the same name as the old non-Gradle project and keep the same package.
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
add a comment |
Since I was using the method "Migrate by creating a new empty project strategy" I created a directory and application named myprojectgradle and the package generated was com.example.myprojectgradle where my previous package was com.example.myproject. I fixed the package but the -gradle suffix was present in some places and confusing Android Studio.
I changed the package in the generated unit test files (not important and are just boilerplate) and also removed the -gradle suffix in the build.gradle file applicationId property.
Probably when you are using that strategy you should name your new project with the same name as the old non-Gradle project and keep the same package.
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
add a comment |
Since I was using the method "Migrate by creating a new empty project strategy" I created a directory and application named myprojectgradle and the package generated was com.example.myprojectgradle where my previous package was com.example.myproject. I fixed the package but the -gradle suffix was present in some places and confusing Android Studio.
I changed the package in the generated unit test files (not important and are just boilerplate) and also removed the -gradle suffix in the build.gradle file applicationId property.
Probably when you are using that strategy you should name your new project with the same name as the old non-Gradle project and keep the same package.
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
Since I was using the method "Migrate by creating a new empty project strategy" I created a directory and application named myprojectgradle and the package generated was com.example.myprojectgradle where my previous package was com.example.myproject. I fixed the package but the -gradle suffix was present in some places and confusing Android Studio.
I changed the package in the generated unit test files (not important and are just boilerplate) and also removed the -gradle suffix in the build.gradle file applicationId property.
Probably when you are using that strategy you should name your new project with the same name as the old non-Gradle project and keep the same package.
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
answered Nov 29 '18 at 15:10
PavitxPavitx
42112
42112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529431%2fafter-migrating-old-android-project-to-gradle-r-is-unknown%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you try this: stackoverflow.com/questions/17054000/…
– user3474985
Nov 28 '18 at 23:15
Yes, that pointed me in the right direction. See my answer below. Thanks.
– Pavitx
Nov 29 '18 at 15:12