Uploaded image for project: 'Couchbase Lite'
  1. Couchbase Lite
  2. CBL-146

Custom Conflict resolution is throwing exception for iOS app when trying to resolve conflict

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.6.0
    • 2.6.0
    • iOS
    • Security Level: Public
    • iOS, emulator iPhone-8-plus
    • Critical

    Description

      Custom Conflict resolution is throwing exception for iOS app when trying to resolve conflict

      Steps to reproduce the issue -
      1. Checkout https://github.com/couchbaselabs/mobile-testkit.git
      2. Checkout branch - feature/cbl-2.6-custom-conflict
      3. Deploy iOS app using Xcode for build 2.6.0-137. (latestbuild app will not have CCR changes, so deploy locally built app )
      4. Run the test -
      pytest -rsx -s --skip-provisioning --timeout 3600 --liteserv-version=2.6.0-137 --liteserv-host=localhost --liteserv-port=8080 --no-conflicts --enable-file-logging --delta-sync --sync-gateway-version=2.5.0 --mode=cc --server-version=6.0.1-2037 --liteserv-platform=ios --create-db-per-test=cbl-test -k test_local_wins_custom_conflicts["pull"] testsuites/CBLTester/CBL_Functional_tests/TestSetup_FunctionalTests/test_custom_conflicts.py

      CCR API code is available at - https://github.com/couchbaselabs/mobile-testkit/blob/feature/cbl-2.6-custom-conflict/CBLClient/Apps/CBLTestServer-iOS/CBLTestServer-iOS/Server/ReplicatorConfigurationRequestHandler.swift#L278

      Attachments

        1. cbl_client_ios.log
          163 kB
        2. logs1562687183.603713.zip
          14 kB
        3. Screenshot 2019-07-09 21.14.15.png
          Screenshot 2019-07-09 21.14.15.png
          2.37 MB
        4. stacktrace.png
          stacktrace.png
          1.60 MB

        Activity

          People

            hemant.rajput Hemant Rajput
            hemant.rajput Hemant Rajput
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              PagerDuty