1. 19 Jan, 2018 2 commits
  2. 18 Jan, 2018 1 commit
  3. 17 Jan, 2018 1 commit
  4. 15 Jan, 2018 1 commit
  5. 12 Jan, 2018 1 commit
  6. 11 Jan, 2018 2 commits
  7. 08 Jan, 2018 1 commit
  8. 02 Jan, 2018 6 commits
  9. 19 Dec, 2017 1 commit
  10. 18 Dec, 2017 1 commit
    • George Nash's avatar
      IOT-582 Android build generate universal APK · 4b4a289f
      George Nash authored
      Two major modifications:
      1) The aar file no longer adds the TARGET_ARCH to the
      name of the file. The aar file contains all of the
      architectures that were built upto that point. This
      has been the case for quite a while so the architecture
      in the name only indicated the build that created the
      aar file not the contents of the aar file.
      
      2) When APK files are built it will try to build all
      possible architectures as well as the universal APK
      file.
      
      Bug: https://jira.iotivity.org/browse/IOT-582
      Change-Id: I11f5db9f4cb8c634afe4417b280e5feec6c3d7e9
      Signed-off-by: George Nash's avatarGeorge Nash <george.nash@intel.com>
      4b4a289f
  11. 13 Dec, 2017 1 commit
    • Philippe Coval's avatar
      resource: Fix occlientbasicops to support coaps · 0f2ae826
      Philippe Coval authored
      The fix is to do querry only on resource's address (to use CoAPs channel)
      
      Observed issue was:
      
       ./ocserverbasicops
      
        ./occlientbasicops -u 0 -c 0 -d 1 -p 0 -t 2
        (...)
      
        INFO: occlientbasicops: Callback Context for GET query recvd successfully
        INFO: occlientbasicops: StackResult: OC_STACK_UNAUTHORIZED_REQ
        INFO: occlientbasicops: SEQUENCE NUMBER: 16777216
        INFO: PayloadLog: NULL Payload
        INFO: occlientbasicops: =============> Get Response
      
      I fixed it to:
      
        INFO: occlientbasicops: StackResult: OC_STACK_OK (...)
        INFO: PayloadLog: Payload Type: Representation (...)
        INFO: PayloadLog:     URI:/a/led (...)
        INFO: PayloadLog:             state(bool):false (...)
      
      Extra note, it look like the parse function is never returning false.
      
      Change-Id: Id3e48c8a04453e87a09e7636ead9a9f64c499d44
      Bug: https://jira.iotivity.org/browse/IOT-2390
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23637/Signed-off-by: default avatarPhilippe Coval <philippe.coval@osg.samsung.com>
      (cherry picked from commit f6394a48)
      0f2ae826
  12. 11 Dec, 2017 1 commit
  13. 08 Dec, 2017 4 commits
  14. 04 Dec, 2017 1 commit
    • Senthil Kumar G S's avatar
      [ES] Changes in Easysetup for spec compliance. · 36c7f823
      Senthil Kumar G S authored
      It includes the following:-
      1. [IOT-2909] Exclude read-only properties.
      Read-Write interface response for "/WiFiConfResURI" is currently
      including the read-only properties ("swat" and "swet") which is incorrect.
      These read-only properties should not be added in the "oic.if.rw" response
      for '/WiFiConfResURI'.
      
      2. [IOT-2910] Handling post request to "/WiFiConfResURI" with baseline
      interface when there is no interface in the query paramter.
      
      3. [IOT-2911] Remove "href" from the baseline response for "/WiFiConfResURI".
      
      Change-Id: I730efa70cedda4dbdb1f21df6e38fec657bc9bb7
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
      36c7f823
  15. 30 Nov, 2017 1 commit
  16. 29 Nov, 2017 1 commit
  17. 23 Nov, 2017 2 commits
    • Senthil Kumar G S's avatar
      [IOT-2906][ES] Remove "href" from child response. · d698f81a
      Senthil Kumar G S authored
      For requests which come directly to child resources
      (/WiFiConfResURI, /CoapCloudConfResURI and /DevConfResURI),
      this patch will remove the "href" property from the response
      as spec doesn't mandate the addition of "href" in the response.
      
      And also, CTT expects the response from direct request to any child
      to be same as the response which comes for the same child
      through collection.
      
      For example:
      Properties in "rep" for '/WiFiConfResURI' should be same as
      the properties in the direct response for GET from '/WiFiConfResURI' resource.
      
      Currently "href" is not included in "rep" for child resources.
      But it is included in the direct response for GET/POST.
      When CTT compares both responses, it finds them different due of "href".
      
      This patch resolves the issue and still conforms to spec.
      
      Change-Id: I017bed18d3e0ad568b662a03d9bd80134538a8c0
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
      d698f81a
    • Senthil Kumar G S's avatar
      [IOT-2904][ES] Fix for issues found through CTT. · fb2e25fc
      Senthil Kumar G S authored
      1. If one of the resources in the POST request over batch
      has invalid properties, then the response should include an
      empty "rep" for those resources.
      For all other resources with valid properties in the request,
      "rep" should include all the properties.
      
      2. Allowing "cn" property to be set to ES_CONNECT_NONE.
      
      Change-Id: Ib819bed7a126717cc56df0fb32b3d9f3ec570682
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
      fb2e25fc
  18. 22 Nov, 2017 2 commits
  19. 20 Nov, 2017 2 commits
  20. 18 Nov, 2017 1 commit
  21. 17 Nov, 2017 1 commit
  22. 15 Nov, 2017 2 commits
  23. 14 Nov, 2017 3 commits
  24. 09 Nov, 2017 1 commit
    • Mats Wichmann's avatar
      Prepare for scons3: change prints and more · 630bb71b
      Mats Wichmann authored
      A previous change updated all the scons scripts:
      
      https://gerrit.iotivity.org/gerrit/#/c/22525/
      
      This change picks up the semi-external scripts that are called
      by the build, and thus are run in the scons context and need updating.
      
      Print statements are surrounded with parens so they look like function
      calls.  This is an scons3 syntax requirement even if still using Python 2.
      
      The old exception format "except FooErr, err" is no longer supported
      in Python 3; since the Python 3 format "except FooErr as err" has been
      available since Python 2.6, there is no problem switching these and it
      makes sense to remove one way things could fail if Py3 is used.
      
      A few comparisons which used <> are changed to the preferred != form.
      
      Reformatted Builder call without changing it, and added a comment in the
      forked version to help explain why there are two copies of UnpackAll.py.
      
      With these changes, a full build completes successfully using scons3.0.
      
      Change-Id: Ia8df28d12c6504d6466dcf793779535d1ad3aa8b
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      (cherry picked from commit b34da4aa)
      630bb71b