Cloud db error: java.net.socketexception connection reset (CloudDB:Invalid dimension size: 0)

[CtrlGirls]

Hi, I am having a problem with Cloud DB in my app. When I open the screen or try to add a value it opens a notifier that says “java.net.socketexception connection reset”. Another person has also the same problem with her apps and she is very far away, so I don’t think it is a problem with the network configuration. I also tried with firebase but it didn’t work.

[TIMAI2]

Is SSL checked / unchecked ?
Is this in companion or compiled? If companion are you using the latest version, 2.78 ?

I have run a quick test here ( I am probably far away as well), all works as it should on companion app:

[CtrlGirls]

I unchecked SSL because it said “com.google.appinventor.components.runtime.errors.YailRuntimeError: Invalid dimension size: 0”, and I updated the companion to the latest version.

[TIMAI2]

SSL needs to be checked.

Ah yes, I see this error when trying to call and empty tag set with create empty list if valueNotThere:

com.google.appinventor.components.runtime.errors.YailRuntimeError: Invalid dimension size: 0 at com.google.appinventor.components.runtime.util.YailMatrix.<init>(YailMatrix.java:39) at com.google.appinventor.components.runtime.util.YailMatrix.fromJsonArray(YailMatrix.java:460) at com.google.appinventor.components.runtime.util.JsonUtil.getObjectFromJson(JsonUtil.java:356) at com.google.appinventor.components.runtime.CloudDB.GotValue(CloudDB.java:1056) at com.google.appinventor.components.runtime.CloudDB$3$1.run(CloudDB.java:805) at android.os.Handler.handleCallback(Handler.java:1070) at android.os.Handler.dispatchMessage(Handler.java:125) at android.os.Looper.dispatchMessage(Looper.java:333) at android.os.Looper.loopOnce(Looper.java:263) at android.os.Looper.loop(Looper.java:367) at android.app.ActivityThread.main(ActivityThread.java:9331) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:837)

To work around this, which is a current bug, you can set valueNotThere with a dummy list (with content) and then test for this with an if statement, before actually adding your list.

Blocks something like this:

This bug should be fixed in the next update