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.

    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.

  • Building Android debug applications using 32-bit SDK can fail because ldd runs out of address space. This failure creates an error message similar to this one:

    C:\KanziWorkspace_3_6_4_1234/3rdpartysdks/android-ndk-r10e/toolchains/arm-linux-androideabi-4.9/prebuilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld.exe: fatal error: C:\KanziWorkspace_3_6_1_266\cm\runtime\examples\Cluster\Application\output\android\ES2_Debug\libkanzi.so: mmap: failed to allocate 345763260 bytes for output file: Not enough space
collect2.exe: error: ld returned 1 exit status

    Workaround: Use the 64-bit NDK. For example, for Windows download and install https://dl.google.com/android/repository/android-ndk-r10e-windows-x86_64.zip.

  • 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>

  • During the installation Kanzi Connect copies the Kanzi Connect application template to the default Kanzi workspace even when you select to install Kanzi Connect to a location that is different from the default Kanzi workspace.

  • To generate Java bindings, you must install the Android gradle platform package.

  • Android ANT workflow does not support the latest Android features. The demo server APK that comes with the SDK issues a warning that the SDK version is obsolete. If you need the APK for the gradle server with the latest updates, submit a support request through the Kanzi Support Portal at http://support.rightware.com.

  • In Kanzi Studio when you export an application with a kzb player for Windows, Kanzi Studio in some cases fails to copy the Kanzi Connect Kanzi Engine plugin.

    Workaround: When the copying fails, manually copy the Kanzi Connect Kanzi Engine plugin from <KanziConnectInstallation>/SDK/output/Win32/plugin/GL_vs2015_Release_DLL/connect_services.dll to the application player directory.