Android Realm version upgrade error with gradle -


we developing android application sdk. sdk module app. using realm in sdk (for now). gradle file i've added realm sdk build.gradle file. i've added apply plugin: 'realm-android' on top of file , 

buildscript {     repositories {         jcenter()     }     dependencies {         classpath "io.realm:realm-gradle-plugin:0.90.1"     }  }

on bottom of file. compiling , working correctly until tried upgrade latest version (1.1.0).

if change version 1.0.0 or later, doesn't compile. here error logs: gradle console:

note: processing class transactionupdateapicall note: processing class address note: creating defaultrealmmodule persistentdatamanager.java:134: error: no suitable method found    findallsorted(string,sort,string,sort,string,sort)             objects = query.findallsorted(sorts.get(0).fieldname,sorts.get(0).dir,sorts.get(1).fieldname,sorts.get(1).dir,sorts.get(2).fieldname,sorts.get(2).dir);                            ^ method realmquery.findallsorted(string,sort) not applicable   (actual , formal argument lists differ in length) method realmquery.findallsorted(string) not applicable   (actual , formal argument lists differ in length) method realmquery.findallsorted(string[],sort[]) not applicable   (actual , formal argument lists differ in length) method realmquery.findallsorted(string,sort,string,sort) not applicable   (actual , formal argument lists differ in length) note: input files use unchecked or unsafe operations. note: recompile -xlint:unchecked details.

the messages window displays error messages gradle build:

error:(134, 32) error: no suitable method found          findallsorted(string,sort,string,sort,string,sort) method realmquery.findallsorted(string,sort) not applicable (actual , formal argument lists differ in length) method realmquery.findallsorted(string) not applicable (actual , formal argument lists differ in length) method realmquery.findallsorted(string[],sort[]) not applicable (actual , formal argument lists differ in length) method realmquery.findallsorted(string,sort,string,sort) not applicable (actual , formal argument lists differ in length) error:execution failed task ':sdk:compilereleasejavawithjavac'. > compilation failed; see compiler error output details.*

if create sample app , add realm (last version) app gradle build file, works. issue realm used sdk module.

if had similar issues , resolved them, or have idea wrong, please share it. appreciated.

thanks in advance.

edit:

the fix had comment used deprecated methods, , compile. compiler showing realm objects missing. once deprecated methods commented out, build succeeded.

realm-java changelog:

  • 0.90.0

deprecated

realm.allobjects*(). use realm.where(clazz).findall*() instead.

realm.distinct*(). use realm.where(clazz).distinct*() instead.

dynamicrealm.allobjects*(). use dynamicrealm.where(classname).findall*() instead.

dynamicrealm.distinct*(). use dynamicrealm.where(classname).distinct*() instead.

realm.allobjectssorted(field, sort, field, sort, field, sort). use realmquery.findallsorted(field[], sort[]) instead.

realmquery.findallsorted(field, sort, field, sort, field, sort). use realmquery.findallsorted(field[], sort[]) instead.

realmquery.findallsortedasync(field, sort, field, sort, field, sort). use realmquery.findallsortedasync(field[], sort[]) instead.

realmconfiguration.setmodules(). use realmconfiguration.modules() instead.

realm.refresh() , dynamicrealm.refresh(). use realm.waitforchange()/stopwaitforchange() or dynamicrealm.waitforchange()/stopwaitforchange() instead.

  • 0.91.0

breaking changes: removed @deprecated methods.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more