Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Importing "Existing Android Code into Workspace" causes an error #7

Closed
precipice opened this issue Oct 16, 2013 · 10 comments
Closed

Importing "Existing Android Code into Workspace" causes an error #7

precipice opened this issue Oct 16, 2013 · 10 comments
Assignees
Labels

Comments

@precipice
Copy link

Project doesn't import into current Android Developer Tools:

2013-10-16 at 11 54 am

(Note: I'm new to Android development and could entirely possibly be screwing this up somehow.)

@jimdanz
Copy link

jimdanz commented Oct 18, 2013

OK, I get the same error when I try to Import is as existing Android code.

@moeadham
Copy link

I can confirm this also, I have android-17 and import fails with the same message.

@shazeline
Copy link

I'm also having the same issue.

@VicV
Copy link

VicV commented Mar 20, 2014

I also got this. However, I continued the imports anyway and then right-clicked the project, and then clicked Android Tools > Fix Project Properties

Project works fine now.

@phillco
Copy link

phillco commented Mar 26, 2014

Ah, so it appears to work if you use "Import Existing Projects into Workspace" as opposed to "Import Existing Android Code (weird):

screen shot 2014-03-25 at 8 55 45 pm

I'll look into why the "Android" import doesn't work, but for now, just use the first import. (Android development will still be enabled). Or use Android Studio — we have gradle files now!

@phillco phillco changed the title Basic README instructions seem to be wrong Importing "Existing Android Code into Workspace" causes an error Mar 26, 2014
@VicV
Copy link

VicV commented Mar 26, 2014

Hmmm its interesting to me that the stripe 'library' has a res file. Importing as non-android makes sense given that this is an sdk, but generally speaking to have your project counted as an android 'library' you should not have a res folder.

@phillco
Copy link

phillco commented Mar 26, 2014

I can look into it — @VicV, want to add an issue?

@VicV
Copy link

VicV commented Mar 26, 2014

@phillco looking into all of it shortly, will do.

@stephen stephen self-assigned this Jul 11, 2014
@stephen
Copy link
Contributor

stephen commented Jul 11, 2014

I've documented the above solution for eclipse in README.md 😄

@stephen stephen closed this as completed Jul 11, 2014
@precipice
Copy link
Author

Thanks, @stephen!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants