Android Question WebView Closes app when open ( GOOGLE -> Scary night )

[scsjc]

Hello everyone, today I found a very strange thing that had never happened to me.

-When I launch the app I have a WebView that loads any information.
-Well, in the 2nd load of the application it gives the error when load WebView.. I put error here below.

I have only been able to solve it in the following way.

1-Disable Chrome (it was by default for webview)
2-Update WebView (I don't know if it was necessary but I have updated it)
3-Load the app ... and it works correctly (1 time, 2 times...)
4-I turn to Enable Chrome (and it goes back to default for webview)
.... As of this moment it has already worked correctly.

I imagine that something in the Chrome cache has caused it to crash when loading the WebView in the app, and I would like to know if there is any way to prevent it from crashing. (I have it set between TryCatch and it doesn't work, it hangs anyway)

** Activity (main) Resume **
main_activity_resume
-----BEGIN CRASHPAD MINIDUMP-----
-----BEGIN CRASHPAD MINIDUMP-----
=hK+J>aZMjPg%GY6,S(Mx_gunHwN7qdz0Y^PPP[tcvf>AFBs-wCc^IYnca1J}K\]|dnv5_guY+aplm9t5.......................
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/dreamltexx/dreamlte:9/PPR1.180610.011/G950FXXSBDUA3:user/release-keys'
Revision: '10'
ABI: 'arm64'
pid: 31509, tid: 31509, name: .packagename  >>> com.packagename <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
    x0  0000000000000000  x1  0000007dfed541ec  x2  7265646f63654400  x3  726f7463656c6553
    x4  0000000000000000  x5  0000000000000000  x6  716e7362646b6452  x7  7f7f7f7f7f7f7f7f
    x8  0101010101010101  x9  0000007dfeab1000  x10 0000007800027428  x11 0000007dfed54488
    x12 00000000ffffffff  x13 0000000000000000  x14 4b3d092f234ec266  x15 cae6c696f68e9634
    x16 0000007e02dfa0f0  x17 0000007e995e2490  x18 0000000013344490  x19 0000000000000003
    x20 0000000000000000  x21 000000780001fdc0  x22 0000007ffd5ec838  x23 0000007800027428
    x24 0000007800027438  x25 0000000000000000  x26 0000007ffd5ecad0  x27 0000000000000000
    x28 00000078000b8270  x29 0000007ffd5ec790
    sp  0000007ffd5ec760  lr  0000007e01d859dc  pc  0000007e01d859dc
backtrace:
    #00 pc 00000000034529dc  /data/app/com.android.chrome-Bmxzn5LYbgb338zgpAEO7Q==/base.apk (offset 0xa0f000)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/dreamltexx/dreamlte:9/PPR1.180610.011/G950FXXSBDUA3:user/release-keys'
Revision: '10'
ABI: 'arm64'
pid: 31509, tid: 31509, name: .packagename  >>> com.packagename <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
    x0  0000000000000000  x1  0000007dfed541ec  x2  7265646f63654400  x3  726f7463656c6553
    x4  0000000000000000  x5  0000000000000000  x6  716e7362646b6452  x7  7f7f7f7f7f7f7f7f
    x8  0101010101010101  x9  0000007dfeab1000  x10 0000007800027428  x11 0000007dfed54488
    x12 00000000ffffffff  x13 0000000000000000  x14 4b3d092f234ec266  x15 cae6c696f68e9634
    x16 0000007e02dfa0f0  x17 0000007e995e2490  x18 0000000013344490  x19 0000000000000003
    x20 0000000000000000  x21 000000780001fdc0  x22 0000007ffd5ec838  x23 0000007800027428
    x24 0000007800027438  x25 0000000000000000  x26 0000007ffd5ecad0  x27 0000000000000000
    x28 00000078000b8270  x29 0000007ffd5ec790
    sp  0000007ffd5ec760  lr  0000007e01d859dc  pc  0000007e01d859dc
backtrace:
    #00 pc 00000000034529dc  /data/app/com.android.chrome-Bmxzn5LYbgb338zgpAEO7Q==/base.apk (offset 0xa0f000)

 

[scsjc]

https://www.facturaone.com/google-afecto-a-aplicaciones-importantes-como-gmail-chrome-y-facturaone/

 

[scsjc]

GOOGLE -> Scary night (I have had a stressful night !!!)
Coinciding with the launch of the production version of my app in AAB format, my app closed and I did not know why
I had users who told me that it did not work and it was happening to me continuously.
(And that I had before the precaution of testing on the BETA channel with test users)

After reviewing everything, I find a routine that calls a WebView was the culprit that the app closed without further ado.

Researching online I have found the previous article, in which Google comments that it is an error and they are working to solve it.

After all this unpleasant situation, I would like to know if anyone has considered making a native WebView? or is it not worth it?

Thank you very much to all
Good night

 

[Addo]

I vote with you for a native b4x browser / webview I would pay for such thing

 

[Erel]

After all this unpleasant situation, I would like to know if anyone has considered making a native WebView? or is it not worth it?

Building a full browser is something that only huge companies can do. Even Microsoft stopped developing their browser and switched to Chromium, the open source project behind Chrome and other browsers.

If you are using WebView to show some rich text then you can consider using BBCodeView instead. A bit complex example: https://www.b4x.com/android/forum/t...todon-pleroma-social-networks.124214/#content

 

[scsjc]

Building a full browser is something that only huge companies can do. Even Microsoft stopped developing their browser and switched to Chromium, the open source project behind Chrome and other browsers.

If you are using WebView to show some rich text then you can consider using BBCodeView instead. A bit complex example: https://www.b4x.com/android/forum/t...todon-pleroma-social-networks.124214/#content

I understand, well we will have to continue using the webview ...

 

[scsjc]

Building a full browser is something that only huge companies can do. Even Microsoft stopped developing their browser and switched to Chromium, the open source project behind Chrome and other browsers.

If you are using WebView to show some rich text then you can consider using BBCodeView instead. A bit complex example: https://www.b4x.com/android/forum/t...todon-pleroma-social-networks.124214/#content

Every day one learns from mistakes
Today's lesson is: DO NOT RUN A WEBVIEW when loading the application.

 

[tufanv]

Every day one learns from mistakes
Today's lesson is: DO NOT RUN A WEBVIEW when loading the application.

bad thing is, google admob uses webview for some types of ads I think, which causes apps to crash at startup when loading interstitital ad

 

[scsjc]

bad thing is, google admob uses webview for some types of ads I think, which causes apps to crash at startup when loading interstitital ad

Yes, everything that is depending on a third party is a problem, because you never know where a problem can appear.

 

[romario87027]

[URL unfurl = "true"] https://www.hwupgrade.it/news/telef...i-google-rilascia-il-fix-ecco-come-sistemare- il-problema_96424.html [/ URL]

I have solved