3

Background

I'm using the Clean architecture in my android app. My domain and data layer are heavily RxJava-based (RxAndroid).I'm also using Parse(BaaS).

Question

I know that the Android Parse SDK is doing a lot of work under the hood like caching and encrypting data. Is it really stable to use its synchronous calls with RxJava's Schedulers?
I know that Retrofit works well with RxJava. Should I drop the Parse SDK and use their REST API instead ?

Help me, I'll give you a cookie !

Rami Jemli
  • 2,550
  • 18
  • 31
  • I assume the exception is thrown during a later api call? can you detail how/where the exception is thrown? – njzk2 Dec 02 '15 at 20:44
  • Sorry, I'll update my question. I'm not using the parse sdk anymore. I chose their REST API because there's a possibility to have my own api in the future. When that happens, I'll only change the api urls instead of the whole code in the data layer. Plus, code is much cleaner with Retrofit. – Rami Jemli Dec 02 '15 at 21:50

1 Answers1

1

I know that the Android Parse SDK is doing a lot of work under the hood like caching and encrypting data. Is it really stable to use its synchronous calls with RxJava's Schedulers?

Parse has plenty of android SDK samples on git etc. If your Rx is friendly with Curl maybe you could also look at REST api from parse.

Otherwise, in the 'Rx' request/response circuit you should try to expose the http traffic ( headers that contain parseAppId, and parseUserToken )

The token mention in the exception

scroll down till 'handling invalid session token'.....

Robert Rowntree
  • 6,230
  • 2
  • 24
  • 43
  • Thank you. I'm not using the parse sdk anymore. I chose their REST API because there's a possibility to have my own api in the future. When that happens, I'll only change the api urls instead of the whole code in the data layer. Plus, code is much cleaner with Retrofit. – Rami Jemli Dec 02 '15 at 21:54