Unexpected Value from Nativegetenabledtags: 0

Unexpected value from nativeGetEnabledTags: 0

I just ran into this problem, too. As a workaround I'm filtering the LogCat output with the following expression on the by Log Message field of the filter:

^(?!.*(nativeGetEnabledTags)).*$ 

Otherwise it is so spammed it's almost useless.

Following Laksh suggestion, if you want to filter this always without having to always write it on the Search for messages field:

1. Goto your Logcat
2. In the Saved Filters part on the left, click on the Edit selected logcat filter (If Saved Filters is not visible then click on Display Saved Filters View in the Logcat)
3. There, in the by Log Message field, enter ^(?!.*(nativeGetEnabledTags)).*$.

logcat filled with message Unexpected value from nativeGetEnabledTags: 0 - how to get rid of this?

Check this answer: Unexpected value from nativeGetEnabledTags: 0

Add this filter to the LogCat: ^(?!.*(nativeGetEnabledTags)).*$

It is a bug introduced in the latest revision of the tools... Google is working on a fix on the next version.

Unexpected value from nativegetenableTags 0

There is no need of downgrading the sdk for removing that warnings, you can filter the warnings by using Filter tag Regular Expressions. Just place the below line in Logcat search bar so that all the nativegetenable tags will be removed. This is the problem with API Level 17 SDK and cannot be removed except for filter option.

^(?!.(nativeGetEnabledTags)).$

copy, paste the above line so that all your warning messages with nativegetenabled tags will removed.

Apply Logcat filter ^(?!.*(nativeGetEnabledTags)).*$ in Console

just pipe the output from the script and grep out the problematic log statements. i don't know the script of which you speak, but here's what i do from the command line.

adb logcat | grep -v nativeGetEnabledTags

it appears this does not work for JS's script since it does some trickery with stdout to determine the terminal width. if stdout is grep, then this won't work. you can get around this by commenting out line 28,29 and 135, but you lose the nice line wrapping.

android emulator continuously showing a log cat message

SDK uptation may corrupt your existing file.So you download new SDK bundle for your platform from the following link.
https://developer.android.com/sdk/index.html.

---

Related Topics