kroll | Kroll itself is the microkernel and set of base | Mobile library

I'm not sure, how to solve this problem with SDK version 8.3.1, but when I switched to 9.0.0 and imported Firebase Dynamic Links dependency through Gradle instead of using plain .aar and .jar dependencies, it started working properly.

There is absolutely no need of Hyperloop for this.

You can communicate with the actionBar using the activity https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Android.Activity

Then you can fetch the actionBar from the activity, and then change the icon using the icon property of the actionBar

Make sure to do this only after the window has triggered the open event though.

First of all, read the bluetooth overview. Check if bluetooth permissions have been added to the project.

One thing that is wrong here is that isConnected=true is set too early, because you can consider that you are connected after ble services has been discovered and (status == BluetoothGatt.GATT_SUCCESS). Otherwise, you can't read and write characteristics.

A good starting point can be this repo from google. It is old project and I'm not sure if you have to update some dependency to make it compile, but nothing important.

Establish a connection and start reading bytes is easy, but if you want establish a reliable connection with ble device, due to android fragmentation and manufacturerers that don't follow the bluetooth specs, it can be super difficult, almost imposible to make a bluetooth low energy that works perfect for all devices.

Once you have started to read some bytes, I suggest this video to learn some important tricks about. If you want go deeper, read carefully this fantastic resource about ble.

Once you start to get desperate with ble, probably it will be a good moment to read this list of known issues

Finally, you will discover that the best thing that you can do with ble low energy in android is use open source libraries like the Nordic semiconductor ble library or RxAndroid Ble.

But before use a ble library, it is a good practice understand what is doing the library and understand why you need it.

EDIT: I have never used appcelerator, but here you have a bluetooth module for appcelerator titanium.

You can convert text representing Javascript objects (JSON) in PHP using json_decode

Example:

Fixed, changed JAVA path and JAVA_HOME from environment variables to a 64-bit Java Installation. Before it was set to 32-bit JAVA.

NOTE: You still need 32-bit JAVA for Appcelerator Studio and Titanium SDK to work properly.

From the flutter docs:

In 12cR1 you could do something like:

There 3 main difeferences between SOAP 1.2 and SOAP 1.1

1. SOAP 1.2 uses "application/soap+xml" as Content-Type and SOAP 1.1 uses "text/xml".

2. SOAP 1.2 does not use SOAPAction header line.

3. SOAP 1.2 uses "http://www.w3.org/2003/05/soap-envelope" as the envelope namespace and SOAP 1.1 uses "http://schemas.xmlsoap.org/soap/envelope/".

The good example which I got from resource: http://www.herongyang.com/Web-Services/Perl-SOAP-1-2-Request-Differences-SOAP-1-1-and-1-2.html is below

This is a known issue with appcelerator and basically, it hasn't been fixed for certain configurations - the devs have been having difficulty reproducing the error, so it seems the exact version choice for titanium and node is important.

"Path must be a string. Received undefined" error is thrown if you build to Android using Node 6.X.X strictly with Appc CLI

Resolution: Won't Fix

One user's fix.

The developer has closed the issue and there is conflict about whether the issue has been solved.

Will close ticket as won't fix. Confirmed that I do not get this error any more with
Appc CLI Core 5.4.0-36 with Ti SDK 6.0.0.v20160728020336.

and

I am still unable to reproduce this issue with the current GA stack:
Appc CLI NPM: 4.2.8
Appc CLI Core: 6.1.0
SDK: 6.0.1.GA
Node: v6.9.2
OS: Mac OS X (10.12.2)
If possible, when running the mobile project, include the debug and trace logs: DEBUG=* appc run -l trace.

Now you're using:

Titanium (6.0.1.GA - CLI 5.0.14)
Node (6.11.2)

Try using older sdks for titanium and an earlier node version. I don't see it being an issue with the Android sdk.

One user resolved it by downgrading node

I resolved it by using node v4x. It does not work with v6.x which I was using when I saw the error.

From github:

appcelerator/titanium Path must be a string. Received undefined

From the devs:

The obvious check of all paths:

The first thing I would do is look at both your Appc CLI and Titanium CLI config files and see if there are any settings that look like paths that are undefined, null, or empty and fixing them. You can find them at ~/.appcelerator/appc-cli.json and ~/.titanium/config.json.

and downgrading versions:

So this happens because of some changes in Node.js that affect 5.5.1.GA. If your app needs to stay on SDK 5.5.1.GA try to downgrade your Node version to a 4.X version, otherwise upgrading to SDK 6.0.1.GA should fix the issue.

The other issue that is always worth mentioning - is to uninstall and install fresh sdks, in case there's been some changes or flaw in the current ones that were imported with the project you've inherited.