Java lang runtimeexception ошибка андроид

asked Jan 14, 2011 at 5:37

It is a problem of your Intent.

Please add your Activity in your AndroidManifest.xml.

When you want to make a new activity, you should register it in your AndroidManifest.xml.

You may be trying to find the view before onCreate() which is incorrect.

public class MainActivity extends Activity {

  ImageView mainImage = (ImageView) findViewById(R.id.imageViewMain); //incorrect

  @Override
  protected void onCreate(Bundle savedInstanceState){
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
  }
  ...
}

answered Nov 18, 2013 at 13:50

answered Dec 6, 2011 at 15:38

In my case I forgot to add the google maps library

<application>
    ....

    <uses-library android:name="com.google.android.maps" />
</application>

Also, check that you’re not missing the preceding dot before the activity path

<activity android:name=".activities.MainActivity"/>

answered Apr 29, 2011 at 10:43

It also happens because of this issue. I unchecked the jars that needed be exported to the apk and this same thing happened. Please tick the jars that your app Needs to run.

answered Jul 2, 2013 at 11:35

This might not be relevant to the actual question, but in my instance, I tried to implement Kotlin and left out apply plugin: 'kotlin-android'. The error happened because it could not recognize the MainActivity in as a .kt file.

Hope it helps someone.

answered Dec 13, 2016 at 18:08

I encountered this problem too, but in a slightly different way. Here was my scenario:

App detail:

• Using ActionBarSherlock as a library
• Using android-support-v4-r7-googlemaps.jar in the ActionBarSherlock library so I could use a «map fragment» in my primary project
• Added the jar to the build path of my primary project
• Included the <uses-library android:name="com.google.android.maps" /> in the manifests of both the library project and my primary project (this may not be necessary in the library?)
• The manifest in the primary project had the proper activity definition and all of the appropriate properties
• I didn’t have an abstract activity or any of the other gotchas I’ve seen on Stack Overflow pertaining to this problem.

However, I still encountered the error described in the original post and could not get it to go away. The problem though, was slightly different in one regard:

• It only affected a fresh install of the application to my device. Any time the app installed for the first time, I would get the error preceded by several «warnings» of: Unable to resolve superclass of FragmentActivity
• Those warnings traced back to the ActionBarSherlock library
• The app would force close and crash.
• If I immediately rebuilt and redeployed the app, it worked fine.
• The only time it crashed was on a totally fresh install. If I uninstalled the app, built and deployed again from Eclipse, it would crash. Build/deploy a second time, it would work fine.

How I fixed it:

• In the ActionBarSherlock library project, I added the android-support-v4-r7-googlemaps.jar to the build path

• This step alone did not fix the problem

• Once the jar was added to the build path, I had change the order on the Java Build Path > Order and Export tab — I set the JAR to the first item in the list (it was the last after the /src and /gen items).

• I then rebuilt and redeployed the app to my device — it worked as expected on a fresh install. Just to be certain, I uninstalled it again 2-3 times and reinstalled — still worked as expected.

This may be a total rookie mistake, but I spent quite a while digging through posts and my code to figure it out, so hopefully it can be helpful to someone else. May not fix all situations, but in this particular case, that ended up being the solution to my problem.

answered Oct 12, 2012 at 12:29

This error can also be the ultimate sign of a dumb mistake (like when I — I mean, cough, like when a friend of mine who showed me their code once) where they try to execute code outside of a method like trying to do this:

SQLiteDatabase db = openOrCreateDatabase("DB", MODE_PRIVATE, null); //trying to perform function where you can only set up objects, primitives, etc

@Override
public void onCreate(Bundle savedInstanceState) {
....
}

rather than this:

SQLiteDatabase db;

@Override
public void onCreate(Bundle savedInstanceState) {
db = openOrCreateDatabase("DB", MODE_PRIVATE, null);
....
}

answered Oct 29, 2013 at 20:15

For me, my package string in AndroidManifest.xml was incorrect (copied from a tutorial).
Make sure the package string in this file is the same as where your main activity is, e.g.

 package="com.example.app"

An easy way to do this is to open the AndroidManifest.xml file in the «Manifest» tab, and type it in the text box next to Package, or use the Browse button.

Also, the package string for my activity was wrong, e.g.

<activity android:name="com.example.app.MainActivity" android:label="@string/app_name">

I (stupidly) got the same error weeks later when I renamed my package name. If you do this, make sure you update the AndroidManifest.xml file too.

Jagdeep SinghJagdeep Singh

1,1901 gold badge16 silver badges34 bronze badges

answered Jul 16, 2014 at 6:01

saji159saji159

3287 silver badges14 bronze badges

For me it was different from any of the above,

The activity was declared as abstract, That is why giving the error.
Once it removed it worked.

Earlier

     public abstract class SampleActivity extends AppcompatActivity{
     }

After removal

     public class SampleActivity extends AppcompatActivity{
     }

answered Jan 9, 2020 at 12:30

Ok, I am fairly experienced on the iPhone but new to android. I got this issue when I had:

Button infoButton = (Button)findViewById(R.id.InfoButton);

this line of code above:

@Override
public void onCreate (Bundle savedInstanceState) {
}

May be I am sleep deprived 😛

answered Jun 19, 2012 at 15:09

In my case, I was trying to initialize the components(UI) even before the onCreate is called for the Activity.

Make sure your UI components are initialized/linked in the onCreate method after setContentView

NB: This is my first mistake while learning Android programming.

answered Apr 12, 2019 at 16:20

J.G.SebringJ.G.Sebring

5,8841 gold badge30 silver badges42 bronze badges

Brian ReinholdBrian Reinhold

2,3113 gold badges25 silver badges44 bronze badges

Amit SinghAmit Singh

5094 silver badges6 bronze badges

Another reason of this problem may be a missing library.

Go to Properties -> Android and check that you add the libraries correctly

answered Mar 7, 2013 at 10:39

This can happen if your activity class is inside a default package. I fixed it by moving the activity class to a new package. and changing the manifest.xml

before

activity android:name=".MainActivity" 

after

activity android:name="new_package.MainActivity"

Shailendra MaddaShailendra Madda

20.1k15 gold badges94 silver badges136 bronze badges

kizzx2kizzx2

18.6k14 gold badges75 silver badges81 bronze badges

This error also occurs when you use of ActionBarActivity but assigned a non AppCompat style.

To fix this just set your apps style parent to an Theme.AppCompat one like this.:

<!-- Base application theme. -->
<style name="AppTheme" parent="Theme.AppCompat.Light">
    <!-- Customize your theme here. -->
</style>

answered Dec 5, 2013 at 9:14

SdemblaSdembla

1,60913 silver badges13 bronze badges

In my case, I was trying to embed the Facebook SDK and I was having the wrong Application ID; thus the error was popping up. In your manifest file, you should have the proper meta data:

<meta-data
android:name="com.facebook.sdk.ApplicationId"
android:value="@string/facebook_app_id" />

answered Jul 9, 2016 at 14:52

hexiclehexicle

2,0432 gold badges23 silver badges31 bronze badges

asked Jan 14, 2011 at 5:37

It is a problem of your Intent.

Please add your Activity in your AndroidManifest.xml.

When you want to make a new activity, you should register it in your AndroidManifest.xml.

You may be trying to find the view before onCreate() which is incorrect.

public class MainActivity extends Activity {

  ImageView mainImage = (ImageView) findViewById(R.id.imageViewMain); //incorrect

  @Override
  protected void onCreate(Bundle savedInstanceState){
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
  }
  ...
}

answered Nov 18, 2013 at 13:50

answered Dec 6, 2011 at 15:38

In my case I forgot to add the google maps library

<application>
    ....

    <uses-library android:name="com.google.android.maps" />
</application>

Also, check that you’re not missing the preceding dot before the activity path

<activity android:name=".activities.MainActivity"/>

answered Apr 29, 2011 at 10:43

It also happens because of this issue. I unchecked the jars that needed be exported to the apk and this same thing happened. Please tick the jars that your app Needs to run.

answered Jul 2, 2013 at 11:35

This might not be relevant to the actual question, but in my instance, I tried to implement Kotlin and left out apply plugin: 'kotlin-android'. The error happened because it could not recognize the MainActivity in as a .kt file.

Hope it helps someone.

answered Dec 13, 2016 at 18:08

I encountered this problem too, but in a slightly different way. Here was my scenario:

App detail:

• Using ActionBarSherlock as a library
• Using android-support-v4-r7-googlemaps.jar in the ActionBarSherlock library so I could use a «map fragment» in my primary project
• Added the jar to the build path of my primary project
• Included the <uses-library android:name="com.google.android.maps" /> in the manifests of both the library project and my primary project (this may not be necessary in the library?)
• The manifest in the primary project had the proper activity definition and all of the appropriate properties
• I didn’t have an abstract activity or any of the other gotchas I’ve seen on Stack Overflow pertaining to this problem.

However, I still encountered the error described in the original post and could not get it to go away. The problem though, was slightly different in one regard:

• It only affected a fresh install of the application to my device. Any time the app installed for the first time, I would get the error preceded by several «warnings» of: Unable to resolve superclass of FragmentActivity
• Those warnings traced back to the ActionBarSherlock library
• The app would force close and crash.
• If I immediately rebuilt and redeployed the app, it worked fine.
• The only time it crashed was on a totally fresh install. If I uninstalled the app, built and deployed again from Eclipse, it would crash. Build/deploy a second time, it would work fine.

How I fixed it:

• In the ActionBarSherlock library project, I added the android-support-v4-r7-googlemaps.jar to the build path

• This step alone did not fix the problem

• Once the jar was added to the build path, I had change the order on the Java Build Path > Order and Export tab — I set the JAR to the first item in the list (it was the last after the /src and /gen items).

• I then rebuilt and redeployed the app to my device — it worked as expected on a fresh install. Just to be certain, I uninstalled it again 2-3 times and reinstalled — still worked as expected.

This may be a total rookie mistake, but I spent quite a while digging through posts and my code to figure it out, so hopefully it can be helpful to someone else. May not fix all situations, but in this particular case, that ended up being the solution to my problem.

answered Oct 12, 2012 at 12:29

This error can also be the ultimate sign of a dumb mistake (like when I — I mean, cough, like when a friend of mine who showed me their code once) where they try to execute code outside of a method like trying to do this:

SQLiteDatabase db = openOrCreateDatabase("DB", MODE_PRIVATE, null); //trying to perform function where you can only set up objects, primitives, etc

@Override
public void onCreate(Bundle savedInstanceState) {
....
}

rather than this:

SQLiteDatabase db;

@Override
public void onCreate(Bundle savedInstanceState) {
db = openOrCreateDatabase("DB", MODE_PRIVATE, null);
....
}

answered Oct 29, 2013 at 20:15

For me, my package string in AndroidManifest.xml was incorrect (copied from a tutorial).
Make sure the package string in this file is the same as where your main activity is, e.g.

 package="com.example.app"

An easy way to do this is to open the AndroidManifest.xml file in the «Manifest» tab, and type it in the text box next to Package, or use the Browse button.

Also, the package string for my activity was wrong, e.g.

<activity android:name="com.example.app.MainActivity" android:label="@string/app_name">

I (stupidly) got the same error weeks later when I renamed my package name. If you do this, make sure you update the AndroidManifest.xml file too.

Jagdeep SinghJagdeep Singh

1,1901 gold badge16 silver badges34 bronze badges

answered Jul 16, 2014 at 6:01

saji159saji159

3287 silver badges14 bronze badges

For me it was different from any of the above,

The activity was declared as abstract, That is why giving the error.
Once it removed it worked.

Earlier

     public abstract class SampleActivity extends AppcompatActivity{
     }

After removal

     public class SampleActivity extends AppcompatActivity{
     }

answered Jan 9, 2020 at 12:30

Ok, I am fairly experienced on the iPhone but new to android. I got this issue when I had:

Button infoButton = (Button)findViewById(R.id.InfoButton);

this line of code above:

@Override
public void onCreate (Bundle savedInstanceState) {
}

May be I am sleep deprived 😛

answered Jun 19, 2012 at 15:09

In my case, I was trying to initialize the components(UI) even before the onCreate is called for the Activity.

Make sure your UI components are initialized/linked in the onCreate method after setContentView

NB: This is my first mistake while learning Android programming.

answered Apr 12, 2019 at 16:20

J.G.SebringJ.G.Sebring

5,8841 gold badge30 silver badges42 bronze badges

Brian ReinholdBrian Reinhold

2,3113 gold badges25 silver badges44 bronze badges

Amit SinghAmit Singh

5094 silver badges6 bronze badges

Another reason of this problem may be a missing library.

Go to Properties -> Android and check that you add the libraries correctly

answered Mar 7, 2013 at 10:39

This can happen if your activity class is inside a default package. I fixed it by moving the activity class to a new package. and changing the manifest.xml

before

activity android:name=".MainActivity" 

after

activity android:name="new_package.MainActivity"

Shailendra MaddaShailendra Madda

20.1k15 gold badges94 silver badges136 bronze badges

kizzx2kizzx2

18.6k14 gold badges75 silver badges81 bronze badges

This error also occurs when you use of ActionBarActivity but assigned a non AppCompat style.

To fix this just set your apps style parent to an Theme.AppCompat one like this.:

<!-- Base application theme. -->
<style name="AppTheme" parent="Theme.AppCompat.Light">
    <!-- Customize your theme here. -->
</style>

answered Dec 5, 2013 at 9:14

SdemblaSdembla

1,60913 silver badges13 bronze badges

In my case, I was trying to embed the Facebook SDK and I was having the wrong Application ID; thus the error was popping up. In your manifest file, you should have the proper meta data:

<meta-data
android:name="com.facebook.sdk.ApplicationId"
android:value="@string/facebook_app_id" />

answered Jul 9, 2016 at 14:52

hexiclehexicle

2,0432 gold badges23 silver badges31 bronze badges

asked Jan 14, 2011 at 5:37

It is a problem of your Intent.

Please add your Activity in your AndroidManifest.xml.

When you want to make a new activity, you should register it in your AndroidManifest.xml.

You may be trying to find the view before onCreate() which is incorrect.

public class MainActivity extends Activity {

  ImageView mainImage = (ImageView) findViewById(R.id.imageViewMain); //incorrect

  @Override
  protected void onCreate(Bundle savedInstanceState){
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
  }
  ...
}

answered Nov 18, 2013 at 13:50

answered Dec 6, 2011 at 15:38

In my case I forgot to add the google maps library

<application>
    ....

    <uses-library android:name="com.google.android.maps" />
</application>

Also, check that you’re not missing the preceding dot before the activity path

<activity android:name=".activities.MainActivity"/>

answered Apr 29, 2011 at 10:43

It also happens because of this issue. I unchecked the jars that needed be exported to the apk and this same thing happened. Please tick the jars that your app Needs to run.

answered Jul 2, 2013 at 11:35

This might not be relevant to the actual question, but in my instance, I tried to implement Kotlin and left out apply plugin: 'kotlin-android'. The error happened because it could not recognize the MainActivity in as a .kt file.

Hope it helps someone.

answered Dec 13, 2016 at 18:08

I encountered this problem too, but in a slightly different way. Here was my scenario:

App detail:

• Using ActionBarSherlock as a library
• Using android-support-v4-r7-googlemaps.jar in the ActionBarSherlock library so I could use a «map fragment» in my primary project
• Added the jar to the build path of my primary project
• Included the <uses-library android:name="com.google.android.maps" /> in the manifests of both the library project and my primary project (this may not be necessary in the library?)
• The manifest in the primary project had the proper activity definition and all of the appropriate properties
• I didn’t have an abstract activity or any of the other gotchas I’ve seen on Stack Overflow pertaining to this problem.

However, I still encountered the error described in the original post and could not get it to go away. The problem though, was slightly different in one regard:

• It only affected a fresh install of the application to my device. Any time the app installed for the first time, I would get the error preceded by several «warnings» of: Unable to resolve superclass of FragmentActivity
• Those warnings traced back to the ActionBarSherlock library
• The app would force close and crash.
• If I immediately rebuilt and redeployed the app, it worked fine.
• The only time it crashed was on a totally fresh install. If I uninstalled the app, built and deployed again from Eclipse, it would crash. Build/deploy a second time, it would work fine.

How I fixed it:

• In the ActionBarSherlock library project, I added the android-support-v4-r7-googlemaps.jar to the build path

• This step alone did not fix the problem

• Once the jar was added to the build path, I had change the order on the Java Build Path > Order and Export tab — I set the JAR to the first item in the list (it was the last after the /src and /gen items).

• I then rebuilt and redeployed the app to my device — it worked as expected on a fresh install. Just to be certain, I uninstalled it again 2-3 times and reinstalled — still worked as expected.

This may be a total rookie mistake, but I spent quite a while digging through posts and my code to figure it out, so hopefully it can be helpful to someone else. May not fix all situations, but in this particular case, that ended up being the solution to my problem.

answered Oct 12, 2012 at 12:29

This error can also be the ultimate sign of a dumb mistake (like when I — I mean, cough, like when a friend of mine who showed me their code once) where they try to execute code outside of a method like trying to do this:

SQLiteDatabase db = openOrCreateDatabase("DB", MODE_PRIVATE, null); //trying to perform function where you can only set up objects, primitives, etc

@Override
public void onCreate(Bundle savedInstanceState) {
....
}

rather than this:

SQLiteDatabase db;

@Override
public void onCreate(Bundle savedInstanceState) {
db = openOrCreateDatabase("DB", MODE_PRIVATE, null);
....
}

answered Oct 29, 2013 at 20:15

For me, my package string in AndroidManifest.xml was incorrect (copied from a tutorial).
Make sure the package string in this file is the same as where your main activity is, e.g.

 package="com.example.app"

An easy way to do this is to open the AndroidManifest.xml file in the «Manifest» tab, and type it in the text box next to Package, or use the Browse button.

Also, the package string for my activity was wrong, e.g.

<activity android:name="com.example.app.MainActivity" android:label="@string/app_name">

I (stupidly) got the same error weeks later when I renamed my package name. If you do this, make sure you update the AndroidManifest.xml file too.

Jagdeep SinghJagdeep Singh

1,1901 gold badge16 silver badges34 bronze badges

answered Jul 16, 2014 at 6:01

saji159saji159

3287 silver badges14 bronze badges

For me it was different from any of the above,

The activity was declared as abstract, That is why giving the error.
Once it removed it worked.

Earlier

     public abstract class SampleActivity extends AppcompatActivity{
     }

After removal

     public class SampleActivity extends AppcompatActivity{
     }

answered Jan 9, 2020 at 12:30

Ok, I am fairly experienced on the iPhone but new to android. I got this issue when I had:

Button infoButton = (Button)findViewById(R.id.InfoButton);

this line of code above:

@Override
public void onCreate (Bundle savedInstanceState) {
}

May be I am sleep deprived 😛

answered Jun 19, 2012 at 15:09

In my case, I was trying to initialize the components(UI) even before the onCreate is called for the Activity.

Make sure your UI components are initialized/linked in the onCreate method after setContentView

NB: This is my first mistake while learning Android programming.

answered Apr 12, 2019 at 16:20

J.G.SebringJ.G.Sebring

5,8841 gold badge30 silver badges42 bronze badges

Brian ReinholdBrian Reinhold

2,3113 gold badges25 silver badges44 bronze badges

Amit SinghAmit Singh

5094 silver badges6 bronze badges

Another reason of this problem may be a missing library.

Go to Properties -> Android and check that you add the libraries correctly

answered Mar 7, 2013 at 10:39

This can happen if your activity class is inside a default package. I fixed it by moving the activity class to a new package. and changing the manifest.xml

before

activity android:name=".MainActivity" 

after

activity android:name="new_package.MainActivity"

Shailendra MaddaShailendra Madda

20.1k15 gold badges94 silver badges136 bronze badges

kizzx2kizzx2

18.6k14 gold badges75 silver badges81 bronze badges

This error also occurs when you use of ActionBarActivity but assigned a non AppCompat style.

To fix this just set your apps style parent to an Theme.AppCompat one like this.:

<!-- Base application theme. -->
<style name="AppTheme" parent="Theme.AppCompat.Light">
    <!-- Customize your theme here. -->
</style>

answered Dec 5, 2013 at 9:14

SdemblaSdembla

1,60913 silver badges13 bronze badges

In my case, I was trying to embed the Facebook SDK and I was having the wrong Application ID; thus the error was popping up. In your manifest file, you should have the proper meta data:

<meta-data
android:name="com.facebook.sdk.ApplicationId"
android:value="@string/facebook_app_id" />

answered Jul 9, 2016 at 14:52

hexiclehexicle

2,0432 gold badges23 silver badges31 bronze badges

Все написано. Не выдано разрешение на доступ к местоположению (выдаётся пользователем по запросу или в настройках).