PouchDB doesn't get datas if custom server is down

Issue

Hi there,
we use offline-peristence-toolkit in a JET(4.1.0) hybrid app for Android and iOS. Pouchdb is set properly and does the job in the browser when offline and when REST server is down.
It does the job in real device after build for the offline part, but we can't get any data if our REST server is down. Like if PouchDB/persistence toolkit making a difference if we are offline or if our REST is not accessible. Did you had this kind of issue before?

Info

• Environment: (hybrid app)
  Versions
  • offline-persistence-toolkit: 1.1.1
  • pouchdb: 6.3.4
  • pouchdb-find: 6.3.4
• Platform: (iOS/Android)
• Adapter: (IndexedDB)
• Server: (Custom service REST)

[kentarokinebuchi]

When your REST server is down, what HTTP error code are you getting from a request made to the server?. The Offline framework will fetch from cache if the HTTP error code is in the 500-599 range. Other ranges will not fetch from cache because:
300-399 are redirect errors
400-499 are client errors which should be handled by the client

Hi, thanks for your answer.
What about if we have a 404 exception? How do you manage it in an hybrid app? Any way you know? Any advice about how to manage this kind of error.

[marke-apexit]

In theory, a 404 error should only be returned for an invalid resource. The request reaches the server, it is understood, but the resource is not available. It seems that OPT should consider the resource is no longer available (deleted?). I would also be interested in the OPT behavior if a 404 is received.