Known issuesΒΆ

  • Shared memory adapter does not work with Android applications unless you disable SELinux.

  • Kanzi Connect application does not work on a computer that does not have Kanzi Connect SDK installed.

    Workaround: Ensure that all dependencies required by Kanzi Connect are available.

  • In the Simulator when you add to a Kanzi Connect service methods or events, to see these as triggers and actions in the Kanzi Studio Node Components, in the Kanzi Studio Project you must reselect the node.

  • On Windows platform turning back system clock causes network communication to freeze.

  • On QNX7 armv7 platform the Kanzi Connect Viewport example application can fail if the platform does not support a 24-bit framebuffer without alpha channel.

  • Kanzi Connect Server certificate throws a warning when you initiate a HTTPS connection. For QNX 7.1 https connection is disabled.

    Workaround: Use HTTP.

  • Known limitation in Kanzi Connect services is that the execution context is critical for the service implementation. For example, you can access service properties safely only from the Kanzi Connect main thread context. You can invoke main thread execution by calling the notifyWork() method of a service from any execution context. It causes the work(ConnectWorkItem) method of the service to be called in main thread context.

  • Known limitations in Kanzi Connect Android bindings:

    • Avoid using spaces in the installation directory paths.

    • Passing abstract work items, such as class instances, as work items is not supported.

  • When you define service interfaces that use custom types, you must enter the name of the custom type in camel case starting with a capital letter. If you do not do this, Kanzi Connect generates C++ code that does not compile.

    For example, to define a service that uses custom types:

    <type name="ValidCustomTypeName">
  <field name="inttype"     datatype="int"/>
  <field name="floattype"   datatype="float" />
  <field name="booltype"    datatype="bool"/>
  <field name="stringtype"  datatype="string"/>
</type>

  • When the Kanzi Studio Preview zoom level is exactly 100% it in some cases inaccurately calculates touch event coordinates from the Input Service.

    Workaround: Set the Preview zoom level to a value other than 100% or align the Preview and the application Screen with the top left corner to avoid extra offset on touch coordinates.

  • Service running callback from kanzi::connect::AbstractServiceClient::addSessionRunningSubscription() arrives twice under the normal working conditions.

    Workaround: Prepare the client application for the multiple callbacks or use the kanzi::connect::RunningServicesMonitor() instead.