Failed to connect to localhost, app crashing

[theodoreapeters]

Upon launching app, xintent throws a toast warning saying "Failed to connect to localhost....."

Also any action causes the app to crash, although if the action was toggling one of the monitor settings, the new setting is shown when the app is opened again.

Refer to attached screenshots

When I toggle "Monitor startActivity" from On to Off, the app crashes. When I restart the app notice that "Monitor startActivity" is now Off, as expected.

What causes the crash? Is monitor startActivity truly disabled/enabled after the crash? What's the significance of the connection failure toast warning message?

[2Y2s1mple]

Sorry for the delay reply.

• What causes the crash?
  It depends. Maybe full logcat log would help to diagnose.

• Is monitor startActivity truly disabled/enabled after the crash?
  Mostly, if there is ERROR toast, all functions is not working.

• What's the significance of the connection failure toast warning message?
  It means the injected code is not running well.

ps:
Firstly, this apk is a kind of xposed-module, it relies on some *xposed-Framework to load it properly.
(recommend LSPosed/LSPosed: LSPosed Framework
e.g:

[TheZ3ro]

I have the same error, this is logcat

D/SettingsActivity: handleMessage: SEND_KEYS = sA:false,gCP:true,sB:true,rR:true,sS:true,bS:true,sP:true,xlog:true,qI:true
I/SettingsActivity: SP_key='key_startActivity' SP_val='false'
E/AndroidRuntime: FATAL EXCEPTION: PREF_SEND_THREAD
    Process: com.zwk.xintent, PID: 9128
    java.lang.NullPointerException: Attempt to invoke virtual method 'void java.io.PrintWriter.println(java.lang.String)' on a null object reference
        at com.zwk.xintent.ui.activity.SettingsActivity$2.handleMessage(SettingsActivity.java:92)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:223)
        at android.os.HandlerThread.run(HandlerThread.java:67)

Edit: Ok, apparently the first time you install the module it cannot load and execute the handleLoadPackage function. After a first reboot then the module starts working 👍