Consent SDK brings app to crash.

[FrankyLS]

Hello,

since I implemented the Consent SDK, I'm getting obfuscated errors like these in developer console:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.xxxx.yyyyy <<<

backtrace:

 #00  pc 000000000006d724  /system/lib64/libc.so (tgkill+8)

 #01  pc 000000000006ab44  /system/lib64/libc.so (pthread_kill+64)

 #02  pc 0000000000024118  /system/lib64/libc.so (raise+24)

 #03  pc 000000000001c9bc  /system/lib64/libc.so (abort+52)

 #04  pc 0000000000943070  /data/app/com.android.chrome-1/base.apk

I obfuscated the app id. The exception was already obfuscated by the developer console.

Approx. 0.4% of installed copies are crashing like this.

What could cause that?

[mobileadssdk-a...@google.com]

Hi,

Can you provide more information about the crash? When does the crash occur, and is there more information in the stack trace, for example a webview microdump?

Can you provide a sample application that reproduces the crash?

Regards

Sam

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/29/18 16:10:51 myfran...@gmail.com wrote:

Hello,

since I implemented the Consent SDK, I'm getting obfuscated errors like these in developer console:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.xxxx.yyyyy <<<

backtrace:

 #00  pc 000000000006d724  /system/lib64/libc.so (tgkill+8)

 #01  pc 000000000006ab44  /system/lib64/libc.so (pthread_kill+64)

 #02  pc 0000000000024118  /system/lib64/libc.so (raise+24)

 #03  pc 000000000001c9bc  /system/lib64/libc.so (abort+52)

 #04  pc 0000000000943070  /data/app/com.android.chrome-1/base.apk

I obfuscated the app id. The exception was already obfuscated by the developer console.

What could cause that?

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/26b5174a-a133-47c9-8962-d20d40baeb64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[FrankyLS]

I can't reproduce it by myself so I can't give you a minimalistic example with that bug inside. I tried it a lot to trigger that bug.

That crash backtrace without exception is all what I have. :-(

It is from the health feature of the developer console. I have no idea why the exception itself is obfuscated.

I don't have any customer feedback yet.

It didn't happen on any of my testing devices but some customer seem to ran into this issue. I noticed it after my DSGVO-related update. The changes of that were following:

- Adding the Consent SDK (by downloading from GitHub and including it by myself)

- I duped consentform.html to consentform_de.html and did some translation in the second one.

- I modified ConsentForm.java this way to get support for all languages that the application supports (currently, there is only german with fallback-english):

if (Locale.getDefault().getLanguage().equals("de")) {

    this.webView.loadUrl("file:///android_asset/consentform_de.html");
} else {
    this.webView.loadUrl("file:///android_asset/consentform.html");
}

- AdMob, AdView and all the stuff is encapsulated into a separate class. I added the necessary logic to implement the consent form to that class.

- I didn't change any other class of my application (the Consent SDK implementation was a stand-alone update so the application itself is the exact same one)

During smoking a pipe, I scrolled through the code of Consent SDK and noticed an Intent without error handling, so I modified another piece of code in my copy of Consent SDK:

try {
    Intent browserIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(urlString));
    context.startActivity(browserIntent);
} catch (Exception e) {
    if (Locale.getDefault().getLanguage().equals("de")) {
        Toast.makeText(context, "Fehler beim Öffnen des Links: " + urlString, Toast.LENGTH_LONG).show();
    } else {
        Toast.makeText(context, "Can not open the link. Visit: " + urlString, Toast.LENGTH_LONG).show();
    }
}

The original code looked crash-prone to me yes - After another update, the issue is almost gone, but not completely. The developer console still records crash reports like the one above.

[mobileadssdk-a...@google.com]

Hi Franky,

Thanks for the additional information.

Unfortunately without some more specific details of the crash, there is not much we can do. Ideally we'd need to reproduce locally in order to investigate further.

If you can keep an eye and see if it reproduces again, keep track of what devices, Android versions, and if it's webview related, chromium versions, it appears on, that would be useful.

Also if it's webview related there should be a microdump in the logs when the crash occurs.

It doesn't look like a crash that would be specifically caused by the consent SDK code, it seems to be more system-level.

Regards

Sam

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/a0a6954d-13e5-4883-b40d-8a30ba01b4ed%40googlegroups.com.

[FrankyLS]

Hello,

 

This is all I can get from the developer console:

Samsung Galaxy J3(2016) (j3xlte), 1536MB RAM, Android 5.1

Bericht 1 von 1

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

pid: 0, tid: 0 >>> com.XXXXX.XXXXXX <<<

backtrace:

  #00  pc 000000000003ae9c  /system/lib/libc.so (tgkill+12)

  #01  pc 0000000000017731  /system/lib/libc.so (pthread_kill+52)

  #02  pc 0000000000018347  /system/lib/libc.so (raise+10)

  #03  pc 0000000000014be1  /system/lib/libc.so (__libc_android_abort+36)

  #04  pc 0000000000012f70  /system/lib/libc.so (abort+4)

  #05  pc 00000000000374d3  /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so

Motorola Moto G (5S) (montana_n), 2048MB RAM, Android 7.1

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

pid: 0, tid: 0 >>> com.XXXX.XXXXXXX <<<

backtrace:

  #00  pc 0000000000049c64  /system/lib/libc.so (tgkill+12)

  #01  pc 0000000000047403  /system/lib/libc.so (pthread_kill+34)

  #02  pc 000000000001d555  /system/lib/libc.so (raise+10)

  #03  pc 00000000000190a1  /system/lib/libc.so (__libc_android_abort+34)

  #04  pc 0000000000017104  /system/lib/libc.so (abort+4)

  #05  pc 0000000000799ae3  /data/app/com.android.chrome-2/base.apk

Samsung Galaxy S8+ (dream2lte), 4096MB RAM, Android 7.0

Samsung Galaxy S7 Edge (hero2lte), 4096MB RAM, Android 7.0

Sony Xperia XA (F3111), 2048MB RAM, Android 7.0

Samsung Galaxy S7 (herolte), 4096MB RAM, Android 7.0

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

pid: 0, tid: 0 >>> com.XXX.XXXX <<<

backtrace:

  #00  pc 000000000006f9fc  /system/lib64/libc.so (tgkill+8)

  #01  pc 000000000006cd10  /system/lib64/libc.so (pthread_kill+64)

  #02  pc 0000000000025078  /system/lib64/libc.so (raise+24)

  #03  pc 000000000001cc04  /system/lib64/libc.so (abort+52)

  #04  pc 0000000000943070  /data/app/com.android.chrome-1/base.apk

Sony Xperia XZ (F8331), 3072MB RAM, Android 8.0

Samsung Galaxy S9 (starlte), 4096MB RAM, Android 8.0

Samsung Galaxy S8 (dreamlte), 4096MB RAM, Android 8.0

Sony Xperia XZ (F8331), 3072MB RAM, Android 8.0

Sony Xperia XZ1 Compact (G8441), 4096MB RAM, Android 8.0

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

pid: 0, tid: 0 >>> com.xxxx.xxxxx <<<

backtrace:

  #00  pc 0000000000069f18  /system/lib64/libc.so (tgkill+8)

  #01  pc 000000000001dfe0  /system/lib64/libc.so (abort+88)

  #02  pc 0000000000943070  /data/app/com.android.chrome-Mdj5qjR0kqu4fyrTchb6bQ==/base.apk

Note: I obfuscated the id of my app (com.xxxxxx.xxxxxx instead of the real one)

I merged similar crash logs together (That's why there are multiple devices listed). The crash backtrace is from the first device of that list. The differences are only in the long numbers.

Looks like a crash inside WebView across different vendors and android versions.

In the application that is suffering this, nothing but Consent SDK uses a WebView, because it is a native app. 

Two other apps using the same Consent SDK do use that component and are in fine condition. These are HTML5 hybrid apps.

[mobileadssdk-a...@google.com]

Thanks for the update.

We will see if we can reproduce the issue locally and report back any findings.

Regards

Sam

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/31/18 14:59:35 myfran...@gmail.com wrote:

Hello,

 

This is all I can get in the developer console:

Looks like a crash inside WebView across different vendors and android versions.

In the application that is suffering this, nothing but Consent SDK uses a WebView, because it is a native app. 

Two other apps using the same Consent SDK do use that component and are in fine condition. These are HTML5 hybrid apps.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/1e0ccbfc-c783-48df-9b6b-01b21da1181f%40googlegroups.com.

[mobileadssdk-a...@google.com]

Hi,

This is definitely an issue with chromium, we would need a microdump to investigate this further.

If you are able to reproduce locally please let us know and pass the webview microdump on.

Thanks

Sam

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

[FrankyLS]

?where do I get that microdump

[mobileadssdk-a...@google.com]

Hi Franky,

If its a webview crash, the microdump will be in the console (logcat) logs for the device when the crash occurs.

Regards

Sam

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 06/01/18 14:03:50 myfran...@gmail.com wrote:

Where do I get that microdump?

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/95803694-21c3-4166-9808-8399547f4df0%40googlegroups.com.