-
Notifications
You must be signed in to change notification settings - Fork 583
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
no such table in [com.android.tools.build:gradle:2.0.0-beta6] #536
Comments
@s90304a123 show me your model classes! Have they an empty constructor? How is defined the AndroidManifest metadata? |
@jonisaa I'm pretty sure model classes have an empty constructor. And my AndroidManifest metadata like this :
I change android plugin version to : |
@s90304a123 When you where working with the plugin version 1.5.0 of Gradle, your code works correctly? |
@jonisaa Yes, when I downgrade to 1.5 version of |
@s90304a123 It's strange, because I have a project with the latest gradle beta plugin working fine. When working with gradle beta plugin, which version of gradle do you use? I work with gradle 2.10 distribution. |
I'm also seeing this issue. Sugar was working fine before trying to upgrade tools/gradle but gives an error finding USER Table after upgrading. Old Settings |
I realized that I'm using Sugar 1.3. I'm in the process of updating to 1.5. I'll report back with results. |
Ok, I have confirmed this is an issue with Sugar 1.5 as well. |
@mikecole20 could you share your logs? could you create a repo on github with this problem? so we can reproduce it? |
I've run into a similar problem, but it's only an issue if I build from Android Studio - everything is fine if I build from command line. Not sure if there's anything else I can contribute. |
I also experienced this issue (see #542) and found that disabling the experimental 'Instant Run' feature resolved it. Edit: To be a little more specific, this issue only occurred after updating Android Studio from 2.0-beta4 to 2.0-beta6. |
Thanks for the tip @ed-george - disabling instant run did fix it. I've also updated to 2.1.0-alpha1 and this fix works there as well. |
No problem @WoogieNoogie, for the meantime I would suggest that disabling the feature is the current workaround and should be documented as such. Currently in which channel is 2.1.0-alpha1 available? I will try to verify that too. |
It's up on Jcenter, you can use it without updating Android Studio, but the version of AS that forces the update to it is in the Canary channel. |
I've also noticed it's only a problem after a clean install. If you have a working build on the device/emulator built with 1.x.x and then upgrade to 2.x.x, it will continue to work until you uninstall. |
@mikecole20 I can confirm that the issue only occurred once the app was uninstalled, however the AS version migration I had problems with was from 2.0.0-beta4 to 2.0.0-beta6. 2.0.0-beta4 seemed to work as expected for me. |
Android Instant run is a problem. disable it and remove your build folder. |
Any updates on this issue? |
use sugar 1.5 |
1.5 didn't solve the InstantRun issue |
have you guys added the following information in the manifest http://satyan.github.io/sugar/getting-started.html and in the Application? |
@sibeliusseraphini yes definitely, I didn't just start using SugarORM |
Instant Run now works #564 |
fixed with #564 @firasalkafri |
gracias @ ed-george me ayudó mucho |
I found in [com.android.tools.build:gradle:2.0.0-beta6]
always get No such table error...
I trace the source to here class :
com.orm.util.ReflectionUtil
getAllClasses
method always return 0 lengthCould you fix this bug?
The text was updated successfully, but these errors were encountered: