-
Notifications
You must be signed in to change notification settings - Fork 581
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" on SNAPSHOT and works fine on 1.5 #683
Comments
i have a suggestion: the problems about instantRun, multidex and incompatibility wiith new gradles are caused by same piece of code: the code to find model class to create TABLE i suggest to REMOVE completely that code and make a init method that as model classed as paramethers like
is not to much to ask to developer to specify all model classes and this resolve all of that problem |
Agree with the comment above. Would be great to have an explicit way to initialize Sugar. Without classes parsing etc. Using both latest snapshot and 1.5 with properly set up proguard still throws this exception on about 5% of devices |
Sugar is scanning models inside your If your modes are not there you will get no table error. |
@Anfet models are there. Proguard is configured properly. Works for 95% users, 5% get the crash |
@Anfet same code and same configuration works with sugar 1.5 and not with snapshot. and only for few devices. |
@aviadmini I opened a merge request for that feature : #692 |
@RossinesP Thanks, that's exactly what I was looking for. I've only got a few tables and it seems silly to have the whole app fall over just for the sake of some magic auto detection of the model that only saves a few lines. |
same code using sugar 1.5 works on all platform without problem.
using SNAPSHOT version on samsung s4 with android 5.0 i receive no such table but on other device works fine
classpath 'com.android.tools.build:gradle:2.2.0'
public class App extends SugarApp {}
instantRun disabled
could be this commit ? 92301ea
The text was updated successfully, but these errors were encountered: