Exception thrown after the content type is changed about vault HOT 11 CLOSED

Can you please post the entire stacktrace?

from vault.

This probably happens due to #97 - since the upgrade process fails (at runtime), the generated code does not correspond to your schema.

from vault.

Rest of the stacktrace:

at a.b.c.Obj$$ModelHelper.fromCursor(Obj$$ModelHelper.java:49) at a.b.c.Obj$$ModelHelper.fromCursor(Obj$$ModelHelper.java:11) at com.contentful.vault.SqliteHelper.fromCursor(SqliteHelper.java:145) at com.contentful.vault.QueryResolver.all(QueryResolver.java:51) at com.contentful.vault.FetchQuery.resolveAll(FetchQuery.java:30) at com.contentful.vault.FetchQuery.resolveFirst(FetchQuery.java:37) at com.contentful.vault.LinkResolver.resourceForLink(LinkResolver.java:197) at com.contentful.vault.LinkResolver.getCachedResourceOrFetch(LinkResolver.java:96) at com.contentful.vault.LinkResolver.resolveLinksForField(LinkResolver.java:67) at com.contentful.vault.LinkResolver.resolveLinks(LinkResolver.java:55) at com.contentful.vault.LinkResolver.getCachedResourceOrFetch(LinkResolver.java:100) at com.contentful.vault.LinkResolver.resolveLinksForField(LinkResolver.java:67) at com.contentful.vault.LinkResolver.resolveLinks(LinkResolver.java:55) at com.contentful.vault.LinkResolver.getCachedResourceOrFetch(LinkResolver.java:100) at com.contentful.vault.LinkResolver.resolveLinksForField(LinkResolver.java:67) at com.contentful.vault.LinkResolver.resolveLinks(LinkResolver.java:55) at com.contentful.vault.QueryResolver.resolveLinks(QueryResolver.java:80) at com.contentful.vault.QueryResolver.all(QueryResolver.java:64) at com.contentful.vault.FetchQuery.resolveAll(FetchQuery.java:30) at com.contentful.vault.FetchQuery.resolveFirst(FetchQuery.java:37) at com.contentful.vault.FetchQuery.first(FetchQuery.java:57) at com.contentful.vault.FetchQuery.first(FetchQuery.java:53)

This is trigerred by executing the following code:
Vault.with(this, TestSpace.class).fetch(Obj.class).where("name = ?", name).first();

from vault.

This probably happens due to #97 - since the upgrade process fails (at runtime), the generated code does not correspond to your schema.

No, this problem happened with freshly downloaded schema (empty local db before sync).

from vault.

What do you mean by freshly downloaded schema? if the model existed and you've changed it, it is likely that a vault db (even though empty) existed beforehand. You can easily confirm this by simply uninstalling+reinstalling the app, and checking if the exception still happens.

from vault.

I meant app was removed on device and then freshly installed. I also just noticed this happens when there is no data from contentful synced yet.

from vault.

Can you provide a sample project where this issue reproduces?

from vault.

We probably need to work on the same contentful dataset. Maybe it will be easier if we move discussion to the priv?

from vault.

👍 please ping [email protected], I'll pull the ticket once you do. Thanks!

from vault.

It seems this problem exists when running on device with Android 6.0 prerelease version. I tried Android 5.1.1 and cannot trigger this exception anymore. I'd bet a new sqlite version on Android 6.0 is the cause.

from vault.

This turned out to be a side effect of #97, causing a state where the generated code does not correspond with the schema. Issue #99 should prevent such things from happening in the future.

from vault.