When I install my app on Android 4.4 or less I receive this error:

E/AndroidRuntime﹕ FATAL EXCEPTION: main java.lang.NoClassDefFoundError: android/os/PersistableBundle at java.lang.Class.getDeclaredMethods(Native Method) at java.lang.Class.getDeclaredMethods(Class.java:703) at de.greenrobot.event.SubscriberMethodFinder.findSubscriberMethods(SubscriberMethodFinder.java:75) at de.greenrobot.event.EventBus.register(EventBus.java:163) at de.greenrobot.event.EventBus.register(EventBus.java:133) at com.myapp.Domain.Login.Activities.LoginActivity.onCreate(LoginActivity.java:101)

On LoginActivity.java:101 I just have

EventBus.getDefault().register(this);

Rebased off annotations branch. Replacement for PR #174

NB I can't get the annotations branch to build using IntelliJ. Not sure if the Gradle config in the branch has changed or my INtelliJ Gradle config has somehow lost its flavour (this is the only project I touch that uses Gradle).

Hey, this looks like a great library, and I have been exploring using it. I know you guys have quite done quite a bit of research regarding Anotations vs Method Naming, but overall I really feel like Annotations are a much cleaner and more flexible solution.

I added annotations to my local branch. You can create a new EventBus that uses annotations like this new EventBus(DeclarationType.ANNOTATIONS). Then you can subscribe to receive events on any method like this:

@Subscribe public void onMyEvent(CustomEvent e)

This uses the caller chooses thread method. We can also change this by adding an argument.

@Subscribe(threadMode = ThreadMode.Background) public void onMyEvent(CustomEvent e)

This uses the background thread and is definitely a more explicit syntax.

Here is a link to my repo where I implemented the changes. https://github.com/rjbrock/EventBus

I would still need to add unit tests before submitting a pull request so I just wanted to see what your thoughts were first.

Rick

Now that Android Studio 3.2.0 and androidx 1.0.0 libraries have been released, is there a plan to migrate to androidx? Google has said there won't be any more feature releases under the android.support packaging.

Hi, On specific mobiles eventbus crashes with following error.

Fatal Exception: java.lang.NoClassDefFoundError android/telephony/CellInfoGsm de.greenrobot.event.SubscriberMethodFinder.findSubscriberMethods Caused by java.lang.ClassNotFoundException

dalvik.system.BaseDexClassLoader.findClass (BaseDexClassLoader.java:61)

java.lang.Class.getDeclaredMethods (Class.java:703)

de.greenrobot.event.SubscriberMethodFinder.findSubscriberMethods (SubscriberMethodFinder.java:75)

de.greenrobot.event.EventBus.register (EventBus.java:163)

de.greenrobot.event.EventBus.registerSticky (EventBus.java:151)

Looks like findSubscriberMethods is trying to access methods which are marked as @TargetApi(17) while the phone is using api 16. Hence eventbus is not able to find those classes which are not available in api 16. Looks like a bug. Is there any workaround?

The library now requires the use of annotations in order for a method to be subscribed to an event.

@Subscribe public void mySubscribingMethod(MyEvent event)

First of all, thank for project. My question: How to stop onEventMainThread after destroy fragment ?? Some events i don't want to excute after destroy because it maybe no found views and lead to crash app Thanks

Im getting the "classic" error using this library with proguard, but now with r8 the "classic" solution https://stackoverflow.com/a/39387526/3994630 is not working. Any idea?

Hi, if I have an Exception that would normally crash the app within the onEvent callback method the app doesn't crash and the exception is logged by EventBus. Is there a way to change that behaviour to the default one (exception -> crash) ?

I'm trying to use EventBus in my project, but I'm stuck with a strange exception thrown by EventBus when trying to get my App running.

The case is I'm using EventBus in a custom view where I register EventBus in the onAttachToWindow() method and unregister it in the onDetachFromWindow() method. And then I created a method like this:

@Subscribe(threadMode = ThreadMode.MAIN)
public void onEventReceived(MessageEvent event) {
    //TODO
}

The problem is when I run the App, an exception is thrown which is really weird: org.greenrobot.eventbus.EventBusException: Subscriber class XXX and its super classes have no public methods with the @Subscribe annotation

Can anyone help with this? Any suggestions is welcomed.

I've wrestled with this for the past couple of hours or so, but cannot get gradle to build my index. I get the following error: warning: The following options were not recognized by any processor: '[eventBusIndex]'

Here are snippets of my build.gradle file. I also have apt working for dagger 2.0, so I know my apt configuration works:

buildscript {
    repositories {
        mavenCentral()
        maven { url 'https://maven.fabric.io/public' }
    }

    dependencies {
        classpath 'io.fabric.tools:gradle:1.21.5'
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
        classpath 'me.tatarka:gradle-retrolambda:3.2.5'
    }
}

repositories {
    mavenCentral()
}

apply plugin: 'com.android.application'
apply plugin: 'com.neenbedankt.android-apt'
apply plugin: 'me.tatarka.retrolambda'

dependencies {
    compile 'org.greenrobot:eventbus:3.0.0'
    apt 'org.greenrobot:eventbus-annotation-processor:3.0.1'
}

apt {
    arguments {
        eventBusIndex "com.example.EventBusAppIndex"
    }
}

Any pointers on what I may be missing?

Thanks a lot for a fantastic library btw. I've used 2.x version extensively in past projects

It would be nice if there was support for using a coroutines dispatcher to dispatch long running subscribe methods in the background. This would be similar in functionality to ThreadMode.ASYNC. But instead of using a thread pool where each subscribe consumes a thread until it completes, the subscribe method would be able to suspend execution and yield the thread to other subscribers to start processing.

How I'd imagine this would look in Kotlin code would be:

class Obj {
  @Subscribe(threadMode = ThreadMode.COROUTINE) // could also be ThreadMode.SUSPENDABLE
  suspend fun longRunningSubscriber(event: Event) {
    // do something
    // suspend for some long running IO
    // do something else
  }
}

Taking a quick look at the EventBus logic there are a couple things that would need to be implemented/updated.

1. The logic that finds subscribe methods would need to be able to recognize suspendable methods.
   • When Kotlin code is compiled to Java, suspend methods have a Continuation parameter added to the Java method signature.
2. a CoroutinesPoster (similar in concept to AsyncPoster) would need to be created that would dispatch the corresponding suspendable method using a coroutines Dispatcher.

If you don't want to include kotlin/coroutines logic in the main EventBus artifact, I would be fine if this was some sort of optional support that is only available if you import an additional module into the class path & add some configuration to the EventBus object that activates the additional module.

Currently there are a couple possible workarounds to get a coroutine context within a subscriber.

• use runBlocking {} on an ASYNC subscriber which will provide a coroutine context, but this will still block the ASYNC thread until runBlocking completes and doesn't efficiently use threads.
• don't make the subscriber suspendable, but instead launch a background coroutine from the subscriber method to do the long running processing.

I am developing an OpenHarmony application with JavaScript language which used your library, will your library support OpenHarmony platform by JavaScript language? if so, I want to contribute to the OpenHarmony build of this library. Expecte foe your reply!

MyService.java

@Override
public void onCreate() {
    super.onCreate();
    EventBus.getDefault().register(this);
}
@Override
public void onDestroy() {
    super.onDestroy();
    EventBus.getDefault().unregister(this);
}
@Subscribe(threadMode = ThreadMode.MAIN)
public void onMyEvent(MyEvent event){
    Log.e(TAG,"onEvent");
}

MyFragment.java

EventBus.getDefault().post(new MyEvent());

manifast.xml

<application
    android:name="com.xxxx"
    android:allowBackup="true"
    android:icon="@mipmap/ic_launcher"
    android:label="@string/app_name"
    android:supportsRtl="true"
    android:theme="@style/AppTheme"
    android:usesCleartextTraffic="true"
    tools:ignore="GoogleAppIndexingWarning,UnusedAttribute">
  <service android:name=".MyService" />

When we register event listener by sticky, there is a risk of deadlock. Because when register a sticky event, it may invoke the event handler method, if the event handler method tries to acquire a lock to do something, at the same time another thread already acquires the lock and try to post an event, deadlock happend.

If we can optimize the register code to avoid this risk, that will be great!!

I found that there is subscriberInfoIndexes field in SubscriberMethodFinder that can be set to final,And I observe that this field is only assigned in the constructor,So I set this field to final. I don't know if this modification is in line with your expectations.