Repository navigation
Have a problem using Local Datastore in Android after parse server migration #490
Description
I request this issue to parse.com/help.
They said you might report this issue to here.
I try migration to my local parse server.
I succeeded development local parse server.
And my android application connect to this server successfully.
But to use Local Datastore has problem.
I'm using local datastore.
This is my code.
- MyApplication.java
Parse.enableLocalDatastore(this); - userProfileDao.java
try {
ParseQuery query = ParseQuery.getQuery(PARSE_OBJECT);
query.fromLocalDatastore();
mParseObject = query.getFirst();
} catch (ParseException e) {
mParseObject = new ParseObject(PARSE_OBJECT);
}
In userProfileDao.java,
query.fromLocalDatastore(); <- ERROR.... Caused by: java.lang.IllegalStateException: Method requires Local Datastore. Please refer to Parse#enableLocalDatastore(Context).
Before migration, this is no problem.
Currently, I used Parse SDK version 1.13 and Parse server version 2.1.
Please to solve this problem.
Thanks.
Activity
drew-gross commentedon Feb 19, 2016
cc @grantland
shevkorn commentedon Feb 21, 2016
I'm having the same problem, I'm unable to work with local database.
arxidon commentedon Feb 22, 2016
You need to enable the local datastore inside your initialization command, not before like it used to be.
Parse.initialize(new Parse.Configuration.Builder(this) .applicationId("yourappid") .clientKey("yourclientkey") .server("serverurl") .enableLocalDataStore() .build() );shevkorn commentedon Feb 23, 2016
thank you, it works. Very appreciated.
wanclem commentedon Dec 21, 2016
Was having same issue here...Thank you..It worked
rakeshmjiyani commentedon Feb 10, 2017
Work like charm!!
umng commentedon Jul 24, 2017
it works. Thanks
SUMIT5321 commentedon Dec 6, 2017
Thanks, its working
breidest-tbs commentedon Dec 18, 2020
Oh well it is the end of 2020 and I had the same issue.
Can someone please update the Android guidelines
http://docs.parseplatform.org/android/guide/#local-datastore
mtrezza commentedon Dec 18, 2020
Thanks for the reminder @breidest-tbs.
Would you want to open an issue in the docs repo?
If you want to go even further, we would gladly review your PR for the docs change.