IssueTracker

I haven't looks on repro yet, but there is no such thing as AlwaysOnLifecycle in latest versions, LiveData has strong references on all observers (including that were added as observeForever). If nothings keeps a livedata, then it is gced.

ah I see: in observe with Lifecycle we add LiveData as observer to Lifecycle and it keeps it alive. However keeping observerforever + livedata, when nothing has reference on them, is a memory leak by definition: user can't clean this memory anyhow, because neither observer / livedata could be referenced.

It is true, though from usage perspective, it is not obvious at all.

e.g. you are in a class, like a singleton repository where you want to observe the database for some query.
and you write:

MyRepository(dao : MyDao) {
   dao.someLiveData().observeForever(....do something...);
}

And it suddenly stops working :/ which is very non-obvious from the developer's perspective.

If we kept the lifecycle in memory as long as it has observers, wouldn't it solve the problem since they can break the chain by calling stopObserving(observer) ?
When they use observeForever, they are already responsible to remove the observer so I think it is fine?

well, the issue is: no reference on observer, you can't break the chain because you don't have a reference. If you have a reference, LiveData (unfortunately) wouldn't be gc-ed, because even AlwaysActiveObserver inrenally has strong reference on livedata.

It turns out I had an app with the exact above use case: a singleton repository observing a database. The code was working properly with arch components 1.0.0 but unpredictably with 1.1.0. I think this is a good example of a leaky abstraction.
Since I want to observe the database forever with no intention to remove the observer at any point, I had no reason to keep a reference to the LiveData and it ended up being GCed along with the observers in it.
You could also argue that the problem is not with LiveData but with Room using weak references to observers but the developer is not supposed to know the Room implementation details.

I think the real problem is that LiveData has no callback to know that no one wants it anymore; like onReset in Loader.

So there's 2 options for database observers:
1. It either has to un-register observer in onInactive and on next onActive re-query db. Problematic is if nothing has changed you have to filter values or dispatch unnecessarily, and you'll pay the price of query which could be expensive.
2. Register weak observer, or have wear ref to LiveData

Room uses option 2. I created my own LiveData and I used the same (https://bitbucket.org/snippets/Boza-s6/xe8749/sample-livedata-with-features-like-loaders#EmailContentLiveData.java-104), because it was obvious solution, but now I see it will not work in every possible case.

I think there should be statically referenced Lifecycle object to which LiveData subscribes when using observeForever() (and observer is anonymous class, maybe?).

I ran into the same problem yesterday. It tooked me hours to understand what is happening and why my observeForever-observer suddenly stopped being invoked.
I think it is a really bad design that someone should know the implementation details of generated Room DB Code.

I want to use observerForever the same way like i use the simple observe and dont want to ran into problems because of internal implementation details.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bab31cacd4ae98057b694f6ae4c781f5f25ee0c9
Author: Yigit Boyar <yboyar@google.com>
Date:   Wed Oct 31 23:41:00 2018

    Fix live data observe forever in room
   
    This CL fixes a problem where if DAO returned LiveData is
    observed with observeForever but there are no references
    to the LiveData, it would eventually be garbage collected.
   
    To avoid this, InvalidationTracker now manages these LiveData
    objects and strongly references them as long as there is an
    active observer.
    To be 100%, we should actually do it when LiveData has observers
    but right now that API does not exist in the LiveData side
    to get notified when the observer count changes 0 and 1.
   
    I've also cleaned up some test code to avoid duplicating the
    test observers in each test.
   
    I've also added an integration test that uses room w/o any of
    the optional dependencies to ensure that we don't break the
    contract on compileOnly dependencies.
   
    Bug: 74477406
    Test: LiveDataQueryTest, InvalidationTrackerTest, NoAppCompatTestApp
    Change-Id: If88114306d7e20ddaed0312a1203a0d14b710145

M       arch/core-testing/src/main/java/androidx/arch/core/executor/TaskExecutorWithFakeMainThread.java
M       room/compiler/src/main/kotlin/androidx/room/solver/query/result/LiveDataQueryResultBinder.kt
M       room/compiler/src/test/data/daoWriter/output/ComplexDao.java
A       room/integration-tests/noappcompattestapp/.gitignore
A       room/integration-tests/noappcompattestapp/README.md
A       room/integration-tests/noappcompattestapp/build.gradle
A       room/integration-tests/noappcompattestapp/src/androidTest/java/androidx/room/integration/noappcompat/BareDatabaseTest.java
A       room/integration-tests/noappcompattestapp/src/main/AndroidManifest.xml
A       room/integration-tests/noappcompattestapp/src/main/java/androidx/room/integration/noappcompat/BareDatabase.java
M       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/paging/DataSourceFactoryTest.java
M       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/InvalidationTrackerTest.java
M       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/LiveDataQueryTest.java
M       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/QueryTransactionTest.java
A       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/TestLifecycleOwner.java
A       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/TestObserver.java
M       room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/TestUtil.java
M       room/runtime/build.gradle
A       room/runtime/src/main/java/androidx/room/InvalidationLiveDataContainer.java
M       room/runtime/src/main/java/androidx/room/InvalidationTracker.java
A       room/runtime/src/main/java/androidx/room/RoomTrackingLiveData.java
A       room/runtime/src/test/java/androidx/room/InvalidationLiveDataContainerTest.kt
M       room/runtime/src/test/java/androidx/room/InvalidationTrackerTest.java
M       settings.gradle

https://android-review.googlesource.com/810053
https://goto.google.com/android-sha1/bab31cacd4ae98057b694f6ae4c781f5f25ee0c9

FYI this requires client to update to Room 2.1.0-alpha03 but it is fully compatible with 1.x that WM uses.

actually it won't work because the change is in generated code. I'll try to backport itinto WM.

re-opening for WM part.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 3fb46bd8602faaf9c34aa969f8ae589c251c2f72
Author: Yigit Boyar <yboyar@google.com>
Date:   Fri Nov 30 13:19:34 2018

    Track LiveData returned by the WM
   
    This CL works around a bug in Room 1.x where LiveData returned
    by Room might be garbage collected.
   
    Now work manager tracks any live data it returns as long as the
    LiveData is active.
   
    Bug: 74477406
    Test: ObserForeverTest, WorkManagerLiveDataTrackerTest
    Change-Id: I1e45dade1e8a3c29d6c35f7cb0c6e072c68ee658

A       work/workmanager/src/androidTest/java/androidx/work/impl/ObserveForeverTest.java
M       work/workmanager/src/main/java/androidx/work/impl/WorkManagerImpl.java
A       work/workmanager/src/main/java/androidx/work/impl/WorkManagerLiveDataTracker.java
A       work/workmanager/src/test/java/androidx/work/impl/WorkManagerLiveDataTrackerTest.java

https://android-review.googlesource.com/838833
https://goto.google.com/android-sha1/3fb46bd8602faaf9c34aa969f8ae589c251c2f72

Same error message for me. MacOS 10.13, Platform-tools 26.0.2

it seems the version attached in comment#8 actually works on MacOSHighSierra,
(./fastboot version 9dc0875966c0-android ) , but the one (version -4022467) included in 26.0.2 tools release, does not work (it reports the same bug)

I've just flashed fine with the provided version (9dc0875966c0).

jmgao: did we somehow lose this patch when we fixed the Pixel 2 support bug?

Yeah, the fastboot we released was from a separate branch.

Hi, I have a similar issue. I tried to download the latest platform-tools with fastboot version -4022467 but it still tells me:

ERROR: Unable to create a plug-in (e00002be)

How can I fix it?

Thanks for any help.

Not working here too. Am using 26.0.2 platform tools + completely updated High Sierra on MBP 2017.

+1 Stil not working on new MBP running High Sierra, with fully updated platform tools 26.0.2

+1 Still not working new MBP with latest sdk. This is a P1 for us

Platform tools 26.0.2 is not working on High Sierra. I rollback to 26.0.1 and it is working well.

Where can I find 26.0.1?

SOLVED: I have downloaded the fastboot file attached in comment #8 above. Then I have replaced it in the platform-tools folder in sdk and now fastboot works again in High Sierra. I can confirm that the newer version in 26.0.2 does not work as the fixed version in comment #8. NOTE: if the downloaded file has the .dms extension just remove it. It worked for me.

NEW PROBLEM: I think that a similar problem is in the adb because when I issue adb shell I receive the following error:

adb E 11-05 17:05:17   601 15446 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)

Different from the fastboot in platform-tools 26.0.2, adb works despite this error.

Can we get a 26.0.3 revision with the fix? Thanks.

Project: platform/development
Branch: sdk-release

commit 2a75ddf513caf9f971dbecd4474094d5c0f8fcb6
Author: Josh Gao <jmgao@google.com>
Date:   Mon Nov 06 13:29:02 2017

    Update platform-tools version to 27.0.0.
   
    Bug: http://b/64292422
    Test: none
    Change-Id: I1849f0df04af390e8aed716262d2be20efdc3491

M       sdk/plat_tools_source.prop_template

https://android-review.googlesource.com/529912
https://goto.google.com/android-sha1/2a75ddf513caf9f971dbecd4474094d5c0f8fcb6

fastboot version -4022467
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

I install the latest platform-tools via homebrew
I test on my 2016 MacBook Pro 15' with macOS 10.13.1
fastboot still can't work normally

26.0.1

https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip

What's the solution for someone with a Pixel 2 on High Sierra? 26.0.1 works, however 26.0.2 says it's a fix for Pixel 2, so don't want to break anything using .1

Project: platform/development
Branch: master

commit 4592d6f91c24d4cd9f5599c98eebabcb4c3cefcb
Author: Josh Gao <jmgao@google.com>
Date:   Mon Nov 06 13:29:02 2017

    Update platform-tools version to 27.0.0.
   
    Bug: http://b/64292422
    Test: none
    Change-Id: I1849f0df04af390e8aed716262d2be20efdc3491
    (cherry picked from commit 2a75ddf513caf9f971dbecd4474094d5c0f8fcb6)

M       sdk/plat_tools_source.prop_template

https://android-review.googlesource.com/535055
https://goto.google.com/android-sha1/4592d6f91c24d4cd9f5599c98eebabcb4c3cefcb

@29: yeah, sorry for the mess. 26.0.1 works on Mac OS 10.13 but doesn't know about the Pixel 2's extra partitions. 26.0.2 knows about the Pixel 2's extra partitions but doesn't work on Mac OS 10.13. We have 27.0.0 going through QA at the moment that will fix both issues. (Linux and Windows are unaffected: 26.0.2 should be fine for them.) we're also addressing the over-complicated process (too many branches!) that led to this mistake in the first place.

not yet fixed... :(
I hate high Sierra.

Sorry, our platform-tools release is still going through QA. In the mean time, I've attached the binary we're planning to release.

fastboot of #33 works!

Can also confirm the fastboot binary in #33 worked.

Does the new release fix also the same problem with adb shell?

How to use #33 fastboot binary because its not recognized terminal.app

I'm blocked by this too :(

How to use #33 fastboot binary because its not recognized by terminal.app? Is this fastboot binary compressed?

After downloading the binary on OSX, you need to run the command:
chmod +x ./fastboot

Then you should be able to execute it:
./fastboot devices

#########-MacBook-Pro:platform-tools #####$ ./fastboot flashing unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
finished. total time: 7.613s

#41: are you using a direct cable from laptop to device, or going via a USB hub? I've seen problems with some hubs before.

Same problem with ADB on high sierra : Unable to create a plug-in (e00002be)
And can't see my tablet.
 Both, tablet and usb cable, are working fine on my windows.

Same problem, unable to create a plug-in

Fastboot of post #33 worked for me.

I am connecting directly without a hub.

Not work for me!

#33 fastboot gives me an error: permission denied

How do I now it got fix?

I tried sdk-platform-tool for version 26.0.2, and it cannot work.

Comment #33 works, to make it work : go to your finder : Comman + Maj + G, go to usr/local/bin, replace the old fastboot binaries by the old ones, then go to your terminal and run the command chmod +x ./fastboot.
(instead of ./fastboot, drag and drog the fastboot file from the folder to the terminal after chmod +x)

by the new one*

Using #32 fastboot binary flash factory image for pixel, ending with
"""
wiping userdata...
/Users/Admin/Library/Android/sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
"""
is this error related to this issue?

Does mke2fs exist in your directory /Users/Admin/Library/Android/sdk/platform-tools/? Not sure which package were you using, the zip file in #28 doesn't have mke2fs. I guess the configuration might be mixing newer fastboot binary with older package that doesn't have mke2fs?

Yeah, here's the full platform tools zip that has mke2fs alongside fastboot:

Yes, i'm using platform tools 26.0.2, and mke2fs doesn't exit. Thanks for #55 full platform tools zip, it works :)

sdk-repo-darwin-platform-tools-4455170.zip not workin for me.

Same as #57 for me

tried method #8 provided, and even downgrade platform toos to 26.0.1, no lucky.

I cannot unarchive the file from #33 - how can I do that on Mac?

LOL

#33 works. Just need to replace the fastboot binary in /usr/local/bin.

Getting a similar error in adb
"adb E 12-06 00:49:22 16767 1879237 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)"
Anyway related?

The comment #33 + comment #55 worked for me, thanks!

Can someone give a detail instructions or youtube video on how to use this binary in #33 because its not working for a lot of us?

Ive a;lo tried #40 and #63 but in #63. It was no fastboot to replace and still not working even after just putting it in afterward to /usr/local/bin location.

Install the android sdk as you would normally before High Sierra (e.g. install Android Studio or the android-sdk zip) and make sure the platform-tools package is updated. Then replace the fastboot binary in $ANDROID_HOME/platform-tools/ with the one in #33. Additional instructions to install the SDK are on developer.android.com. `which fastboot` should return a full path to fastboot binary.

Thanks #66, I'll try that now...

I'm used just a adb & fastboot files without installing plateform-tools and that's why I don't have the binary. Plus, I'm using the command ----->

Paste this into Terminal:
touch ~/.bash_profile; open ~/.bash_profile

Paste this into your text editor:
export PATH=${PATH}:/Applications/Android

making it able to use in any folder plus not having to use the command "./" in front.

For others reading, change /Applications/Android to where the files "adb and fastboot" are located.

I've got the latest version, and I'm still facing this error

$ brew cask info android-platform-tools
android-platform-tools: 26.0.2
https://developer.android.com/studio/releases/platform-tools.html
/usr/local/Caskroom/android-platform-tools/26.0.2 (1,831 files, 25.5MB)

#68: 27.0.0 is the latest version, downloadable from that link (though the release notes aren't updated yet). if "brew" is giving you an old version, you need to take that up with them...

thanks for clarifying the issue with the release notes.

below is what i'm suggesting the release notes should say (when it's no longer the weekend and i can get someone to review the change). i'll see about getting "update the platform tools release notes" on the Studio release checklist too, so this doesn't get forgotten in future...

#### 27.0.0 (December 2017)

+ Combines the fastboot fixes from 26.0.1 for macOS 10.13 hosts and from
26.0.2 for Pixel 2 devices.

#### 26.0.2 (October 2017)

+ Add fastboot support for Pixel 2 devices. (But reintroduce the macOS 10.13
fastboot bug fixed in 26.0.1.)

Hi, I'm trying to flash latest Oreo 8.1 on nexus 5x but after ./flash-all.sh return me error e00002be. Debug its enabled on lineage, whats the problem?

It seems I am having a very similar issue but upgrading to the newest platform-tools or the above provided files did not help.
I have MacOS High Sierra, and after connecting to a device remotely by calling adb connect 192.168.x.x it says "connected to device xxxx:port_number" but after that I cannot see any device connected and "adb devices" returns nothing.
Connecting over USB works just fine.

this bug is for fastboot (which, other than updating the release notes, is fixed.)

https://issuetracker.google.com/70244520 is for adb.

release notes updated: https://developer.android.com/studio/releases/platform-tools.html.

Am I the only one still having this issue even when using the new platform-tools?

Remember to use ./fastboot from the download folder, not simply fastboot.

WOW! I totally forgot the "./" Sorry Mac noob here. It works. Thanks!

How should i install this new platform-tools to use it with just the command fastboot in terminal (without using the platform-tools directory)?

It still doesn't work!

It still doesn't work for me too.

I have the same problem

no devices/emulators found  @-@!

Not working for me either :/

Doesn't work! Please fix it!

#8
#6/
#80

no longer working for me

This issue marked as fixed for SDK Platform tools version 27.0.1.
please provide below info if this issue reproduces again
1. Host operating system version details
2. SDK Platform tools version
3. ./fastboot --version
4. Android device details

Still failing for me:

1. OSX version: 10.13.3
2. SDK Platform tools version 27.0.1
3. ./fastboot --version: 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)

1. OSX version: 10.12.6
2. SKD Platform tools version 27.0.1
3. fastboot versions:
     -  27.0.0-4455170
     - 9dc0875966c0-android
     - 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)

OSX version: 10.13.3
SDK Platform tools version 27.0.1

./fastboot --version
fastboot version 0.0.1-4500957

./fastboot devices
- no devices

Android device: ASUS Zenpad Z170C (Android 5.0.1)

OSX version 10.13.4
platform-tools_r27.0.1-darwin
LG G3 Europe (lg-d855)

fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/toto/Documents/lg/platform-tools/fastboot

Toto:platform-tools toto$ fastboot devices
Toto:platform-tools toto$
(no output)

./adb devices works fine

Hi Google,

are you going to fix that? Thanks! :)

if a device shows up in `adb devices` it won't show up in `fastboot devices` and vice versa. a device can only be in one of the two modes at any given time.

Yes, that's right. First we test the device in ADB mode: works.
Then we restart the device in fastboot mode: doesn't work.

Really Google can't solve that issue?! :)

I'm having the same issue as described above: adb mode success, fastboot failure
OSX 10.13.4 (17E202)
SDK Platform tools version 27.0.1
fastboot version 0.0.1-4500957
OnePlus 3T running Android 8.0.0

same thing here.. :(

same thing here.. :(

Still this error. This is absolutely ridiculous!

I want to know who has been changing and controlling my phone. Thank you, Cristal Gornto.

Same thing for me also :(

OSX 10.13.5 (17F77)
SDK platform-tools_r28.0.0-darwin
fastboot version 28.0.0-4797878
Galaxy s6 | Android 7

Still Not Working

Is it really that hard to fix this bug for google experts ????
Come on Google do something about it !!!

still does not work :(

sh-3.2# ./fastboot devices
ERROR: Unable to create a plug-in (e00002be)

this is still happening it is not fixed

I have to use a fast boot execute file from like 4 years ago lol

/sdk/platform-tools/fastboot
fastboot version 28.0.0-4797878.it works well

fastbooot command is not working on mac High Sierra

Support only​for​the​future​of​the​same​place​in​USB​debugging​only​to make sure that the product is not the same place as you can imagine​and​be​successful​in​your business with a new one or a long term solution to your problem and the ability to connect with your customers and customers with the best service provider in the world of your business or customer service or service to your company directly from the internet or by phone

#2

K

Google map

On Sat, Sep 1, 2018, 2:33 AM <buganizer-system@google.com wrote:

Google Domin

On Sat, Sep 1, 2018, 2:33 AM <buganizer-system@google.com wrote:

#55 Worked for me. Thanks

Same problem here... fastboot hangs when I give it more than one command:

1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
     -  28.0.1-4986621
4. Android device: Nvidia Shield TV

Similar problem as above here... fastboot gives this error whatever I try (fastboot devices, info, etc):

ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)

1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
     -  28.0.1-4986621
4. android device: anything, does not matter.

tried another mac, only different with the last post is
OSX Version: 10.14.4 Beta (18E194d)

Same issue. macOS 10.14.4 Build: 18E220a

All you motherfuckers are bitches for hacking my phone

Same issue on macOS 10.14.4 (18E226)/ADT 28.0.2

Darwin Kernel Version 18.5.0; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64

Every fastboot command returns:
ERROR: Couldn't create a device interface iterator: (e00002bd)

Same issue for me on macOS 10.14.4 (18E226)

Tried multiple versions of fastboot and it has the same issue.

Same problem:

$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)

macOS: 10.14.4
fastboot:  28.0.2-5303910

Same issue on 10.14.4 (18E226)

ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)

➜  ~ fastboot --version
fastboot version 28.0.2-5303910

Exactly same issue on 10.14.4 (18E226)
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)

Have any solutions? Same here in macos 10.14.4.

macos 10.14.4
fastboot version 28.0.2-5303910

~/Downloads/crosshatch-pq2a.190405.003 ᐅ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
{my_device_id}  fastboot

Still seeing the same kernel console output:
`default        22:37:38.850733 -0700   kernel  495549.216174 fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control`

I'm guessing not _everyone_ is seeing this, else it'd be a higher sev/pri?

maybe similar to this? https://forum.mongoose-os.com/discussion/1719/help-connecting-adafruit-huzzah32-to-new-macintosh

I am having the same issue with fastboot 28.0.2-5303910 after upgrading to macos 10.14.4 and i also see this in the kernel console

fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control

This might be a regression because fastboot version 9dc0875966c0-android from android-platform-tools 26.0.1 is working just fine on macOS 10.14.4

Fixed on any version？

This isn't fixed ... why it's marked with this status :
Status
Fixed

?

10 QT 5602026
Observing the same error while flashing on MAC Sierra ERROR: Couldn't create a device interface iterator: (e00002bd)

android-platform-tools 26.0.1 now does not work on OSX 10.14.5

welp.

Android Debug Bridge version 1.0.41
Version 28.0.3-5475833
Installed as /Users/lengxianfeng/Library/Android/sdk/platform-tools/adb

~/Library/Android/sdk/platform-tools/adb nodaemon server
adb E 06-05 11:10:31 23487 106568 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
Terminated: 15

fastboot version 29.0.0-5611747 - it works)

Unloked

MOSAAD

OBI

All fucking shit off china,delete ittt

Hello easy to you....u get chorme im chorme dev easy so ...no confius again

Android Debug Bridge version 1.0.41
Version 29.0.4-5871666
Installed as /Users/####/Library/Android/sdk/platform-tools/adb

adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:206] Unable to create a device plug-in (e00002be)

on macOS 10.15