Boolean bug calling custom java bl from Android SDK

[Volodymyr_Ialovyi]

Hello @Reece_Smith

I try with your step:

but the boolean field comes right.

Please show how the Information class looks like in your project Demo Service (screenshot where you have signed the Demo Service go to the Information class).

[Volodymyr_Ialovyi]

@Reece_Smith

• Create a table called ‘MyTable’ in backendless with atleast one datatype as a boolean
• Create a Demo Service that accepts that table object as a parameter. I.e:
  public void saveObjectWithBoolColumns(MyTable mtobject) throws InterruptedException
  {
  mtobject.save();
  }
• Deploy service and download it using the download client sdk for android java
• open java project and call the saveObjectWithBoolColumns() passing in an object of MyTable with its boolean datatype set as true. (you will need to set the gradle version of backendless to the latest)
• debug using code runner the data service, when the call hits your service from the android client look at the MyTable object, the boolean you set will be null.

Please try to reproduce with those simple steps that you described, do you have a reproducible problem?

[Volodymyr_Ialovyi]

Hello @Reece_Smith

Thank you for a detailed description of the problem.
I seem to be able to reproduce the problem.
As there will be some additional information, we will inform you in this topic additionally.

[Reece_Smith (Reece)]

Thanks @Volodymyr_Ialovyi , looking forward to seeing the resolution.

[Volodymyr_Ialovyi]

Hello @Reece_Smith

Please test the workaround:
Rename all getters for Boolean fields from getBooleanField to isBooleanField:
from

   public Boolean getBool1 ()
   {
     return bool1;
   }

to

   public Boolean isBool1 ()
   {
     return bool1;
   }

Please write about the result.

[Reece_Smith (Reece)]

Hi @Volodymyr_Ialovyi

That solves the issue if you set the boolean functions to is on the client side

Not sure this will solve the issue on Kotlin, but as a work around we can revert to java classes using is are you guys planning on putting more of a permanent fix in?

Cheers

[mark-piller]

Hi Reece,

I believe the is prefix is the standard convention for the boolean getter in Java. I’d correct @Volodymyr_Ialovyi that it is not a workaround, but actually is the right way to handle that scenario.

Regards,
Mark