Wrong object lifecycle management

[slavchev]

Reported from @wisonye NativeScript/NativeScript#1705

The test phone is a Huawei P8 lite version( Android 5.0 ), it's very easy to re-show the issue, just like my loginUI, if I do type in the "password" field, it will crash( sometimes need to long press to show up the "copy/paste" floating mean to cause crash ), UI super simple, looks like this:

https://drive.google.com/file/d/0B-AooW_48tzISmZCbnNNeDB2ZUU/view?usp=sharing

And here is the crash log output, if your team found something, that's good, if have no idea, then just ignore it, I just want to do a "potential bug report" :)

com.tns.NativeScriptException: No weak reference found. Attempt to use cleared object reference id=366
at com.tns.Platform.getJavaObjectByID(Platform.java:633)
at com.tns.Platform.callJSMethodNative(Native Method)
at com.tns.Platform.dispatchCallJSMethodNative(Platform.java:812)
at com.tns.Platform.callJSMethod(Platform.java:711)
at com.tns.Platform.callJSMethod(Platform.java:690)
at com.tns.Platform.callJSMethod(Platform.java:680)
at com.tns.gen.android.text.TextWatcher_ftns_modules_ui_editable-text-base_editable-text-base_l22_c29__.afterTextChanged(android.text.TextWatcher.java)
at android.widget.TextView.sendAfterTextChanged(TextView.java:7771)
at android.widget.TextView$ChangeWatcher.afterTextChanged(TextView.java:9563)
at android.text.SpannableStringBuilder.sendAfterTextChanged(SpannableStringBuilder.java:976)
at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:520)
at android.text.SpannableStringBuilder.delete(SpannableStringBuilder.java:216)
at android.text.SpannableStringBuilder.delete(SpannableStringBuilder.java:33)
at android.view.inputmethod.BaseInputConnection.deleteSurroundingText(BaseInputConnection.java:249)
at com.android.internal.view.IInputConnectionWrapper.executeMessage(IInputConnectionWrapper.java:398)
at com.android.internal.view.IInputConnectionWrapper$MyHandler.handleMessage(IInputConnectionWrapper.java:82)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5538)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

[slavchev]

I found the problem and I start working on it. The fix won't be shipped with 1.7.0 release. I guess we will provide 1.7.1 after a week or two.

[slavchev]

ping @maknz

[slavchev]

ping @lscown

[NathanaelA]

Shouldn't 1.7.0 be held for this (assuming this is also causing the navigation issues). This is actually a fairly nasty issue and imho a blocking issue.

[slavchev]

Good question. ping @valentinstoychev

[maknz]

I mean, this is probably as serious of an issue as they come. Our app is too unstable to ship in the current state. I understand the complexities around keeping the scope of the 1.7 release as-is and not introducing new things last minute. In reality, whatever is the quickest way to get the fix out, I'm on board with.

[ErjanGavalji]

Hey guys,

We'd rather deliver the goodies we have accumulated already to the community. Fixing the management of the obect lifecycle is our current task. We hope to have 1.7.1 as soon as possible (estimated to some time early next week).

Thank you for your support!

Cheers,
Erjan

[milewski]

i have this bug every time.. costumer already complaining... really,... is there any temporarily work around?

[maknz]

FWIW, 1.7 improved things dramatically for us. I think I saw one crash come through, but our app is basically back to normal after the 1.7 upgrade. Haven't played too much, but try that first if you haven't already.