-
Notifications
You must be signed in to change notification settings - Fork 19
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
Crash within RushCore.initialize() in Android 6.0.1 #110
Comments
I have the same problem. |
Hi, Very sorry for the late replay!! Have a look here: http://www.rushorm.com/advanced.html#Troubleshooting Directly setting your Rush classes should resolve this. The plan for the future is define your model package in the manifest to resolve this. Thanks |
Then, i have other question for you. I have my classes like And, then, following that link i have This gives me an error saying that |
Hi, I that works for me when I copy it. Other than changing Item to
Could you have imported the wrong 'Item' class? Thanks |
Hi, stuart-apadmi [email protected] escreveu no dia terça, 17/05/2016
|
Hi Stuart, I have not been as lucky with my testing on 6.0.1. I followed your suggestion and modified the code to be as below
Then I did a fresh build (clean + make) of my project. 05-18 23:28:41.671 2312-2740/com.gradians.prepwell E/AndroidRuntime: FATAL EXCEPTION: Thread-1664 *Compiled again (no clean, just make) and re-launched * The said class (User) class is declared as follows 05-18 23:36:20.457 8333-8333/com.gradians.prepwell E/AndroidRuntime: FATAL EXCEPTION: main |
The problem seems to be limited to the User class. Commenting all references to User out lets me go ahead. But in terms of declaration,
it is quite like the other classes that were passed to RushInitialize(). So, I am flummoxed. The only difference between User and other classes is that
Is it possible that the User table is not ready when response from Google+ is got back? |
HAve you resolved the problem 3 years after ? |
Hi Stuart,
Love Rush-ORM. But am getting a crash within RushCore.initialize() in Android 6.0.1.
This didn't happen in the earlier versions (4.2+).
The call to RushCore.initialize() is within the onCreate() method - like so
public class App extends Application {
@OverRide
public void onCreate() {
.......
AndroidInitializeConfig config = new AndroidInitializeConfig( this.getApplicationContext() ) ;
RushCore.initialize(config) ; // <--- crashes here
}
}
** Below is the stack-trace from Android Studio. **
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at java.lang.Class.classForName!(Native method)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at java.lang.Class.forName(Class.java:324)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.android.AndroidRushClassFinder.getRushClass(AndroidRushClassFinder.java:58)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.android.AndroidRushClassFinder.getRushClasses(AndroidRushClassFinder.java:45)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.android.AndroidRushClassFinder.findClasses(AndroidRushClassFinder.java:36)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.core.RushCore.loadAnnotationCache(RushCore.java:462)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.core.RushCore.initialize(RushCore.java:122)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at co.uk.rushorm.core.RushCore.initialize(RushCore.java:80)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at com.gradians.prepwell.Prepwell.onCreate(Prepwell.java:36)
05-06 08:30:34.603 5779-5779/com.gradians.prepwell A/art: art/runtime/runtime.cc:399] at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1036)
The text was updated successfully, but these errors were encountered: