Backendless Support

support for old android api

Hey guys,

I have an app with thousands of user with android api 14-19. I've started migration to baclendless v.4, created new app in admin panel, added android sdk v.4.0.1

and I have next error:

  2. java.lang.NoClassDefFoundError: java.util.Objects
  3. at com.backendless.Persistence.find(
  4. at com.backendless.DataStoreFactory$1.find(
  5. at$Register.updateContacts(
  6. at$Register.access$1000(
  7. at$Register$1.handleResponse(
  8. at$Register$1.handleResponse(
  9. at com.backendless.UserService$8.handleResponse(
  10. at com.backendless.UserService$8.handleResponse(
  11. at com.backendless.async.message.AsyncMessage$ResponseHandler.handle(
  12. at com.backendless.async.message.AsyncMessage.handleCallback(
  13. at com.backendless.core.AndroidCarrier$1.handleMessage(
  14. at android.os.Handler.dispatchMessage(
  15. at android.os.Looper.loop(
  16. at
  17. at java.lang.reflect.Method.invokeNative(Native Method)
  18. at java.lang.reflect.Method.invoke(
  19. at$
  20. at
  21. at dalvik.system.NativeStart.main(Native Method)

Also I've found this answer:

So I have reasonable question, how to support my users with old devices?

Can I use backendless v.4 with android backendles sdk v.3, because I have no problem on sdk v.3?

Or I should to write my own rest client to work with api?

It will be friendly from your side to write more recomendations, for example min android api on

Thank you for your work.

Best Regards, Oleg Tarashkevich

Leave a Comment

Comments (2)



the 3.x library will not work with the 4.0 backend.

Your best option is to fork the repo and refactor the code so it does not use any newer Android classes. I think this would be a less labor intensive process than writing your own rest client.




Thank you for your suggestion

have a nice day!