Android: Activity getting Destroyed after calling Camera Intent

Question

I have two Activities, A1 and A2. A1 calls A2 and from A2, I am calling the camera intent as below:

launchIntent = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
launchIntent.putExtra(MediaStore.EXTRA_OUTPUT,photoPath);   
startActivityForResult(launchIntent,CAMERA_REQUEST);

It opens the camera, and I can take the picture. The problem arises once I click the save button (tick button in s3). My onActivityResult function is not called; instead, A2's onDestroy method is called. I have few steps to be done in the onActivityResult function.

I have my manifest like this for my second Activity (A2):

android:configChanges="keyboardHidden|orientation|locale"
android:screenOrientation="portrait

In HTC One X, my onActivityResult function is getting called, but in my S3 second Activity(A2) is getting destroyed.

How can I fix this?

you might want to check regarding `noHistory=true` or ` `Intent.FLAG_ACTIVITY_NO_HISTORY`. See here for details: https://stackoverflow.com/a/62107555/3763032 — mochadwi, May 30 '20 at 19:20

score 84 · Answer 1 · edited Mar 13 '23 at 12:28

84

I have found a solution in this SO post. The issue is that when you click on the "save" button of the camera, the activity call changes the orientation method and it will be destroyed and recreated. Try to set:

android:configChanges="orientation|screenSize"

in the android manifest (not only android:configChanges="orientation" as suggested in this other SO post; it not work for API level 13 or higher).

It prevented the destroy activity for me.

edited Mar 13 '23 at 12:28

Jeff Schaller

2,352
5
23
38

answered May 14 '13 at 14:21

giacomo87

841
5
3

5

android:configChanges="orientation|keyboardHidden|screenSize" http://stackoverflow.com/questions/16154279/galaxy-s3-taking-picture-in-portrait-mode-destroys-activity – NBApps Nov 13 '14 at 15:13
Thanks man, you saved me android:configChanges="orientation|keyboardHidden|screenSize" working perfect. – sandeepmaaram Aug 20 '15 at 09:55
1

I was facing same issue and found that in developer option "Do not keep activities" check were marked. comment for help of other developers. – Khizar Hayat May 05 '17 at 11:05

score 45 · Answer 2 · answered Nov 03 '14 at 05:24

Launching camera requires a lot of memory. So on devices with low memory android system closes the Activities running in background and hence onCreate() is called. Due to this photopath you have given becomes null and you wont be able to get the saved image.

Solution is to save the photopath while system is destroying your activity and then restore it again.

@Override
    public void onSaveInstanceState(Bundle outState) {
        // TODO Auto-generated method stub

            outState.putString("photopath", photopath);


        super.onSaveInstanceState(outState);
    }

    @Override
    protected void onRestoreInstanceState(Bundle savedInstanceState) {
        // TODO Auto-generated method stub
        if (savedInstanceState != null) {
            if (savedInstanceState.containsKey("photopath")) {
                photopath = savedInstanceState.getString("photopath");
            }
        }

        super.onRestoreInstanceState(savedInstanceState);
    }

and in case you are doing this on Fragment.

@Override
    public void onSaveInstanceState(Bundle outState) {
        // TODO Auto-generated method stub

            outState.putString("photopath", photopath));


        super.onSaveInstanceState(outState);
    }

    @Override
    public void onViewStateRestored(Bundle savedInstanceState) {
        // TODO Auto-generated method stub
        if (savedInstanceState != null) {
            if (savedInstanceState.containsKey("photopath")) {
                photopath = savedInstanceState.getString("photopath");
            }
        }

        super.onViewStateRestored(savedInstanceState);
    }

This is the correct answer and this solve the problem. Thanks to give the solution for activity and fragment both. Really nice answer. — Smeet, Nov 13 '14 at 17:49
I am facing the same problem, but my fragment's onSaveInstanceState never gets called. Only my activity's onDestory method gets called. Any solutions? — Sandra, Jan 25 '16 at 09:50
Can you validate your statement, that low memory devices closes activities in backround, by posting some google developer document links. — Sandeep R, Mar 15 '16 at 06:38
Some users are facing this problem but I can't reproduce it. Is it possible to force or emulate this condition ? — fegoulart, Aug 27 '20 at 15:05

score 27 · Answer 3 · answered Nov 17 '13 at 05:50

27

Be sure you don't have the "Don't keep activities" Developer setting on, as it will destroy the activity you are leaving.

answered Nov 17 '13 at 05:50

Omaraf

833
8
15

5

I just wasted A DAY of work trying to figure out what is wrong with my app. Thanks a bunch! – Kaloyan Roussev Oct 15 '15 at 16:58
5

But your App should still work and not crash with "Don't keep activities" on, shouldn't it? – tagy22 Mar 02 '16 at 15:44
Yes, but that is not normal behavior. If you launched an activityForResult and lose Activity A, result of Camera intent won't be able to rebuild activity A anyway. – Omaraf Mar 02 '16 at 18:51
1

Android should be able to re-create it, that's what onCreate() and onSavedInstanceState() are for – Leo supports Monica Cellio Apr 27 '18 at 20:04

score 13 · Answer 4 · answered Apr 15 '13 at 12:27

13

The camera app requires a lot of memory and to free up memory, the operating system has to kill background apps, including yours. This is normal for all Android apps. Your activity will be recreated when the camera app returns. To retain activity state information, override onSaveInstanceState() to store your data and read them back in onCreate().

answered Apr 15 '13 at 12:27

laalto

150,114
66
286
303

ya i too expected the same behaviour as it ll call the onCreate method again but it didnt call the on create of A2 – Sudarshan Apr 15 '13 at 12:34
Can you post the google developer document on your statement.for reference please. – Sandeep R Mar 15 '16 at 06:23

score 2 · Answer 5 · answered Feb 26 '16 at 09:20

My Activity has many tasks running when I am calling Camera Intent.. I have GPS location listeners, and many more tasks.

When it returns from the Camera Intent I need to add marker on a map in the location that the image was taken.. So if the user took more than one picture, it should show markers for each picture..

If it will destroy my Activity each time I call Camera Intent all the information that I had before about markers and their location will be lost.. And also, I will have to initialize the map again. That's a big problem for my app.

And yes, it only happens when I take a picture in Landscape mode. If I take the picture in portrait everything is fine so far..

I will try to use android:configChanges="orientation|screenSize" As suggested here.. Hope it will help!

Well, after add this the manifest, I can say that the problem was gone!! Cheers!. In addition, if this was related to memory, so it should happen also when I am taking portrait images and as I said, it only happens on landscape so it highly make sense that it's because of the orientation and not memory. — Moti Bartov, Feb 26 '16 at 13:53

score 2 · Answer 6 · answered Jul 17 '18 at 10:27

2

For me, it happens when i enable an option in Developer Mode called "Don't keep Activities". After i unchecked it, activity won't recreate while backing from choosing a picture from gallery or from camera app.

answered Jul 17 '18 at 10:27

Shihab Uddin

6,699
2
59
74

Android: Activity getting Destroyed after calling Camera Intent

6 Answers6

Linked

Related