Crashes and ANRs

MIT App Inventor Help
1

Hi,
I tested my app run fine (successful) in my Oppo Android version 13.

should I ignore this error? or how should i fix it? looking for advice on the following error from googleplay console:
Error - Issue 1 of 1 - Detected on 1 device during testing

FATAL EXCEPTION: main
Process: appinventor.ai_jbenedictlow.Cloudifi_Global, PID: 24406
java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1
at java.util.ArrayList.get(ArrayList.java:439)
at com.sunny.CustomWebView.CustomWebView.getIndex(Unknown Source:26)
at com.sunny.CustomWebView.CustomWebView$WebClient.onPageStarted(Unknown Source:10)
at Fa.c(chromium-TrichromeWebViewGoogle.apk-stable-410410683:2)
at Cs.handleMessage(chromium-TrichromeWebViewGoogle.apk-stable-410410683:162)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

2

Hello Jason

It appears to be more than one issue - certainly a warning of "Fatal Exception" should mean your App is actually not running fine at all.

I can see you are using the Custom Web View, which is very robust - are you sure you have implemented it correctly?

Is your App using any other extensions? Are there warnings in the App Inventor Blocks work area?

WARNINGS

3

Hello ChrisWard,
No Error notice.

Screenshot 2023-04-29 20.16.56
Screenshot 2023-04-29 20.16.561238×601 85.8 KB

4
  • Did you get any error messages from the Google Play Pre-launch Report?
  • Are there any negative user comments on this?
  • How many crashes occurred in which period and on which Android versions?
  • Could the crash be reproduced on one of your test devices?

If the answers to questions 1, 2 and 4 are negative, I would ignore the problem for now. If crashes accumulated, you would most likely get reactions from your users.

5

It's also possible that you haven't checked your app enough. Does your app accept any data or values from users? Is it sufficiently secured against entering incorrect data or leaving empty text boxes? Have you checked the various variants of your app's handling well enough?

6

Thank you, Anke and Patry.

Anke: 2 and 4 is nagative. 1 is positive.

Patry: I will check as to your responsed.

7

c4b94f277ad1e7fb95a74d37b1579dd34cd3f51e_2_690x334

I don't support extensions, but this looks fishy.

What is the point of setting something to itself?

8

Then post screenshots of the Pre-launch report (regarding errors).

And please explain to me why you release an app when you already know (from the Pre-launch report) that there will be errors / bugs.

Nobody would do that in a reasonable way, because bad user ratings are then inevitable.

9

You are correct. Somehow this is needed to prevent the zooming or something like it...

10

It is a boolean, so set to true or false (logic blocks)

11

Anke,
app is not released, it is set in googlepaly under internal testing.

12

Show full screenshots of the error message(s).

13

Anke,
here are the sccreenshot

Screenshot 3
Screenshot 31506×774 132 KB

Screenshot 2
Screenshot 21892×817 115 KB

Screenshot internal testing
Screenshot internal testing1163×110 18.3 KB

14

Ok, I had to do some digging to find such an error message in my Pre-launch reports. Your first screenshot is not complete. The affected device should also be listed below. You can click there to display details about the device and see a preview video of the test. Do that and see when the error/crash occurs.

Also let us know which device it is.

15

The vidoe can't be played.
Here the screenshot.

Screenshot 2023-05-01 20.58.05
Screenshot 2023-05-01 20.58.051598×767 64.2 KB

16

I have the same problem with Firefox. Try with Chrome.

17

i am using chrome

18

For me it works fine with Chrome.