runtimeexception

we have an issue in our current app-version with the EventHandler from otto. We get a RuntimeException in our crash-log, with following description: "Reason: java.lang.RuntimeException: Could not dispatch event: classcom.nameOfBrand.ui.events.SwitchFragmentEvent to handler [EventHandler public void com.nameOfBrand.ui.activities.MainActivity.onSwitchFragmentEvent(com.nameOfBrand.ui.events.SwitchFragmentEvent)]" We have a button and in its onClickListener we fire an self-defined SwitchFragmentEvent . In some weird situations, the framework can't dispatch the Event and throws an RuntimeException

Getting elasticsearch "can not run as root" error after upgrading from SonarQube 6.5 to 6.6. Nothing else changed. CentOS release 6.8 (Final) Java(TM) SE Runtime Environment (build 1.8.0_101-b13) java.lang.RuntimeException: can not run elasticsearch as root at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:106) ~[elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:195) ~[elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) [elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap

I've come across the fact that catching RuntimeException is generally considered bad practice because they can't be corrected and usually are programmer errors. However, we have an (insanely) large application where changes in any part can have unforeseen consequences (Yes, this a problem in and of itself) . Now the idea has come up to start catching and logging RuntimeExceptions at the application's top level so we can be more efficient in fixing such bleed issues as they come up. Like every good Java team, we have a lovely zealous Uncle Bob follower who is absolutely forbidding us from doing

I have created a custom camera app using this source code, but on few devices (like on High Resolution Devices) I am getting: RuntimeException setParameters failed I am facing this exception, due to this: params.setPictureSize(1200, 900); And I have noticed, If I use (1600, 1200) instead of (1200, 900) then I am not facing such issues Logcat: 11-07 11:45:20.630: E/AndroidRuntime(3827): FATAL EXCEPTION: main 11-07 11:45:20.630: E/AndroidRuntime(3827): java.lang.RuntimeException: Unable to resume activity {pl.gatti.dgcam/pl.gatti.dgcam.DgCamActivity}: java.lang.RuntimeException: setParameters

An android application that I am currently developing was crashing (fixed that), due to what should have raised an IndexOutOfBoundsException. I was accessing a string in the doInBackground method of a class that extends AyncTask, from the variable arguments parameter (ie String...). I was accidentally accessing index 1 (not 0) of a one element variable argument string (mildly embarrassing...). When the application first crashed I looked at my logcat, (and many times again to confirm that I wasn't insane) and there was no stack trace for a RuntimeException to be found. I crash my phone quite

I try to configure Chromecast but got RuntimeException and don't understant the reason. Here are logs from Fabric: Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{... .activity.TVActivityPhone}: java.lang.RuntimeException: com.google.android.gms.dynamite.DynamiteModule$zza: Remote load failed. No local fallback found. at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2677) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2747) at android.app.ActivityThread.access$900(ActivityThread.java:187) at android.app