Some (?) ReplicatorChange CouchbaseLiteExceptions contain no message

Description

I haven't exhaustively tested, but taking the below example of an unknown hostname, we get the error code of `5002` which maps to the correct error:

https://github.com/couchbase/couchbase-lite-android/blob/677acb372ce407357eb54eaa41dc81e8b6f40832/shared/src/main/java/com/couchbase/lite/CBLError.java#L67

However this should presumably be included in the `CouchbaseLiteException`, rather than requiring a look up of `5002`:

```
ReplicatorChange{replicator=Replicator[<- Database@3379dd6{name='*******'} URLEndpoint{url=ws://***************:4984/*******}], status=Status{activityLevel=STOPPED, progress=Progress{completed=0, total=0}, error=CouchbaseLiteException{domain='CouchbaseLite', code=5002, msg=null}}}
```

Activity

Show:

Blake Meike November 22, 2019 at 11:34 PM

Dan sez "close it"

Blake Meike November 22, 2019 at 2:16 AM

Blake Meike November 22, 2019 at 2:10 AM

It is no longer possible to create a CouchbaseLiteException without an error message. There are some corner cases that might cause an "Unknown Exception", but they should be pretty rare.

Daniel Petersen September 6, 2019 at 2:52 PM

Should do this with our error message unification work.

Jim Borden June 5, 2019 at 5:54 AM

Whoa, has this been sitting around for over a year?  If this is the case this is not a very hard fix to make, nor a big one.  Every error has a corresponding message in LiteCore already ripe for the picking via `c4error_getMessage`.  

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created May 30, 2019 at 7:13 PM
Updated November 22, 2019 at 11:34 PM
Resolved November 22, 2019 at 2:16 AM
Instabug