Dialog throwing "Unable to add window — token null is not for an application” with getApplication() as context

Question

My Activity is trying to create an AlertDialog which requires a Context as a parameter. This works as expected if I use:

AlertDialog.Builder builder = new AlertDialog.Builder(this);

However, I am leery of using "this" as a context due to the potential for memory leaks when Activity is destroyed and recreated even during something simple like a screen rotation. From a related post on the Android developer's blog:

There are two easy ways to avoid context-related memory leaks. The most obvious one is to avoid escaping the context outside of its own scope. The example above showed the case of a static reference but inner classes and their implicit reference to the outer class can be equally dangerous. The second solution is to use the Application context. This context will live as long as your application is alive and does not depend on the activities life cycle. If you plan on keeping long-lived objects that need a context, remember the application object. You can obtain it easily by calling Context.getApplicationContext() or Activity.getApplication().

But for the AlertDialog() neither getApplicationContext() or getApplication() is acceptable as a Context, as it throws the exception:

"Unable to add window — token null is not for an application”

per references: 1, 2, 3, etc.

So, should this really be considered a "bug", since we are officially advised to use Activity.getApplication() and yet it doesn't function as advertised?

Jim

reference for the first item where R.Guy advises using getApplication: http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html — gymshoe, Apr 26 '11 at 21:21
other references: http://stackoverflow.com/questions/1561803/android-progressdialog-show-crashes-with-getapplicationcontext — gymshoe, Apr 26 '11 at 21:22
other reference:http://stackoverflow.com/questions/2634991/android-1-6-android-view-windowmanagerbadtokenexception-unable-to-add-window — gymshoe, Apr 26 '11 at 21:23
http://groups.google.com/group/android-developers/browse_thread/thread/7a648edddccf6f7d — gymshoe, Apr 26 '11 at 21:23
Related: [Android 1.6: "android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an application"](http://stackoverflow.com/q/2634991) — blahdiblah, Jan 11 '13 at 22:23
It's an interesting question. I wish someone would answer your question; **So, should this really be considered a "bug", since we are officially advised to use Activity.getApplication() and yet it doesn't function as advertised?** — Akyl, Apr 29 '13 at 13:30
Possible duplicate of [Android 'Unable to add window -- token null is not for an application' exception](http://stackoverflow.com/questions/7933206/android-unable-to-add-window-token-null-is-not-for-an-application-exception) — Nicolai Weitkemper, Nov 19 '16 at 10:55

score 1404 · Answer 1 · edited Sep 25 '14 at 14:10

1404

Instead of getApplicationContext(), just use ActivityName.this.

edited Sep 25 '14 at 14:10

Knossos

15,802
10
54
91

answered Aug 29 '11 at 11:04

Steven L

15,304
1
21
16

67

Great! Just to comment on that.. you may sometimes need to store "this" globally, (for example) in order to access it within a listener's implemented method who has it's own 'this'. In that case, you'd define "Context context" globally, and then in the onCreate, set "context = this", and then refer to "context". Hope that comes in handy too. – Steven L Sep 11 '11 at 13:04
8

Actually, as `Listener` classes are often anonymous-inner, I tend to just do `final Context ctx = this;` and I'm away ;) – Alex Sep 11 '11 at 16:00
28

@StevenL In order to do what you're saying, you should use ExternalClassName.this to explicitly refer to "this" of the outer class. – Artem Russakovskii Oct 14 '11 at 21:18
11

Wouldn't using "this" leak it if your dialog is used in a callback and you leave the activity before the callback is called? At least that's what Android seems to complain about in logcat. – Artem Russakovskii Oct 14 '11 at 21:20
@StevenL could you add some reasoning behind this? – tidbeck May 08 '12 at 15:16
Thanks for the suggestions. I know using "this" works, but I also have experienced significant memory leaks using "this", which disappear if I avoid using it... – gymshoe Jun 08 '12 at 06:52
How this is work inside receiver, In Broadcast Receiver , onReceiver method have context object of Context, In Broadcast Receiver, we can't use "this" . – Ashish Dwivedi Jan 08 '13 at 06:08
for me i use the "this" by passing it to another class constructor, and that works perfectly ! – S.Thiongane Jun 13 '13 at 15:53
You can use `yourActivity.this` if you are used in function – Pratik Butani Oct 02 '13 at 13:43
6

I would not advise @StevenLs approach as you can easily leak the memory of that activity unless you remember to clear the static reference in onDestroy - Artem is correct. StevenLs approach is bourne from a lack of understanding how Java works – Dori Nov 19 '13 at 11:02
so why does getApplicationContext() gives error @Dori? – Diffy Jun 21 '14 at 19:28
3

by my comment above I'm referring to @StevenL comment above containing "_sometimes need to store `this` globally_". Storing an `Activity` context (which is what `this` is referring to in this case) in a `static` field is a __big__ no-no as its really easy to leak memory. @Artems approach of "`ExternalClassName.this`" is most definitely the correct one. `getApplicationContext()` probably gives the error due to a dialog needing to be attached to the `Activity` context as opposed to the `Application` context... – Dori Jun 22 '14 at 09:25
2

...Android has a bit of ambiguity when it comes to the `Context` class, especially as `Activity` and `Application` both extend context but have differnt external state and in not all situations and truely substitutable for each other, which sort of goes against the __L__ part of __[SOLID](http://en.wikipedia.org/wiki/SOLID_(object-oriented_design))__ OOP design priciples - and hence leads to confusion such as the OPs issue. – Dori Jun 22 '14 at 09:28
Your solution worked for me when I am using ActivityName.this, so I edited your answer so that it will help other also... Generally Devs are assigning Dialog as static so for this they need to use their ActivityName.this instead of getAppLicationContext() – Manish Sharma Sep 25 '14 at 13:53
So basically we get the choice to violate Android's design principles and purposefully leak the activity it's attached to OR miss out on a lot of functionality. – G_V Dec 16 '14 at 13:22
I was at this for ages and didn't know what it was that was the issue! Thanks :) – SmiffyKmc Apr 29 '16 at 13:35
I had an issue with putting my custom api in asynctask, and using myactivity.this as a context worked like a charm. Thanks – Richeek Dey May 02 '16 at 10:46
2

This is not an answer to the question. The question is: Why does AlertDialog.Build(Context context) only work when you pass an Activity as the context? Or, asked the other way: Why doesn't AlertDialog.Build(Context context) work when you pass a context that is not an Activity? – pzulw May 27 '16 at 14:31
1

Or if you're getting this error from within a `Fragment`, use `getActivity()`. – aroth Aug 22 '16 at 07:15
You rocks the day ,super) ActivityName.this. – Kogile Aug 02 '17 at 06:07
i test it bot not working . i fix it with createing currentActivity variable in application class and i set it in all activites. – ali zarei Dec 16 '17 at 17:49
What is `ActivityName` in `PreferenceFragment`? – Dmitry Aug 27 '18 at 21:14

score 200 · Answer 2 · edited Dec 23 '22 at 08:15

200

Using this did not work for me, but MyActivityName.this did.

edited Dec 23 '22 at 08:15

starball

20,030
7
43
238

answered Jun 21 '12 at 00:54

TrueCoke

2,406
1
16
9

65

That's what happens when you use `this` from inside of an inner class. If you want to reference the instance of an outer class, you must specify so, as you do with `OuterClass.this`. Just using `this` always references the most inner class' instance. – kaka Aug 25 '12 at 12:01

score 64 · Answer 3 · edited Jul 08 '16 at 10:53

64

You can continue to use getApplicationContext(), but before use, you should add this flag: dialog.getWindow().setType(WindowManager.LayoutParams.TYPE_SYSTEM_ALERT), and the error will not show.

Add the following permission to your manifest:

<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />

edited Jul 08 '16 at 10:53

Shashanth

4,995
7
41
51

answered Dec 25 '14 at 08:09

codezjx

9,012
5
47
57

1

I get Unable to add window android.view.ViewRootImpl$W@426ce670 -- permission denied for this window type – Ram G. Feb 05 '15 at 23:07
add permission: – codezjx Feb 06 '15 at 02:38
3

Seems like you cannot enable this permission in API 23 onwards https://code.google.com/p/android-developer-preview/issues/detail?id=3123 – roy zhang Sep 17 '15 at 15:12
1

You can use it for API 23 onwards, however you need to prompt the user: startActivityForResult(new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION, Uri.parse("package:" + getPackageName())), OVERLAY_PERMISSION_REQ_CODE); however, whether you _should_ use it is another matter... – Ben Neill Sep 06 '16 at 04:44
2

This is useful when you are showing progress dialog inside service – Anand Savjani Dec 02 '16 at 12:24
1

This also works with `Presentation`, my secondary display doesn't flicker anymore since I've provided my application context as context. – Emre A Dec 20 '19 at 07:56

ONE · Answer 4 · 2017-05-14T00:32:38.933

You've correctly identified the problem when you said "... for the AlertDialog() neither getApplicationContext() or getApplication() is acceptable as a Context, as it throws the exception: 'Unable to add window — token null is not for an application'"

To create a Dialog, you need an Activity Context or a Service Context, not an Application Context (both getApplicationContext() and getApplication() return an Application Context).

Here's how you get the Activity Context:

(1) In an Activity or a Service:

AlertDialog.Builder builder = new AlertDialog.Builder(this);

(2) In a Fragment: AlertDialog.Builder builder = new AlertDialog.Builder(getActivity());

Memory leaks is not a problem that is intrinsic to the "this" reference, which is an object's reference to itself (i.e. reference to the actual allocated memory for storing the object's data). It happens to any allocated memory for which the Garbage Collector (GC) is unable to free up after the allocated memory has outlived its useful lifespan.

Most of the time, when a variable goes out of scope, the memory will be reclaimed by the GC. However, memory leaks can occur when the reference to an object held by a variable, say "x", persists even after the object has outlived its useful lifespan. The allocated memory will hence be lost for as long as "x" holds a reference to it because GC will not free up the memory for as long as that memory is still being referenced. Sometimes, memory leaks are not apparent because of a chain of references to the allocated memory. In such a case, the GC will not free up the memory until all references to that memory have been removed.

To prevent memory leaks, check your code for logical errors that cause allocated memory to be referenced indefinitely by "this" (or other references). Remember to check for chain references as well. Here are some tools you can use to help you analyze memory use and find those pesky memory leaks:

For an Activity you can also use **ActivityName.this** where _ActivityName_ is (obviously) your activity's name (for example MainActivity) — Luis Cabrera Benito, Jul 09 '17 at 04:22

score 34 · Answer 5 · answered Jun 26 '11 at 07:56

Your dialog should not be a "long-lived object that needs a context". The documentation is confusing. Basically if you do something like:

static Dialog sDialog;

(note the static)

Then in an activity somewhere you did

 sDialog = new Dialog(this);

You would likely be leaking the original activity during a rotation or similar that would destroy the activity. (Unless you clean up in onDestroy, but in that case you probably wouldn't make the Dialog object static)

For some data structures it would make sense to make them static and based off the application's context, but generally not for UI related things, like dialogs. So something like this:

Dialog mDialog;

...

mDialog = new Dialog(this);

Is fine and shouldn't leak the activity as mDialog would be freed with the activity since it's not static.

i'm calling it from an asynctask, this worked for me, thx mate — MemLeak, Dec 18 '12 at 15:47
my dialog was static, once i removed the static declaration it worked. — Ceddy Muhoza, Oct 31 '16 at 00:50

score 28 · Answer 6 · answered Apr 24 '18 at 10:41

28

in Activity just use:

MyActivity.this

in Fragment:

getActivity();

answered Apr 24 '18 at 10:41

Mahmoud Ayman

1,157
1
17
27

This fixed it for me in my Activity. Thanks – Werner Jul 06 '18 at 05:53

score 26 · Answer 7 · answered Sep 10 '14 at 01:41

26

I had to send my context through a constructor on a custom adapter displayed in a fragment and had this issue with getApplicationContext(). I solved it with:

this.getActivity().getWindow().getContext() in the fragments' onCreate callback.

answered Sep 10 '14 at 01:41

Grux

584
1
11
20

4

This worked for me too, I passed it to the constructor of external AsyncTask that I am using (It shows a progress Dialog). – Rohan Kandwal Oct 14 '14 at 10:35
3

this is the REAL answer for more complex tasks :) – teejay Dec 12 '14 at 13:13
1

I agree with the @teejay – Erdi İzgi Jul 06 '15 at 20:10

Milad Yarmohammadi · Answer 8 · 2018-10-20T11:54:30.670

22

* kotlin version *

You should pass this@YourActivity instead of applicationContext or baseContext

edited Oct 20 '18 at 11:54

answered Oct 20 '18 at 11:47

Milad Yarmohammadi

1,253
2
22
37

score 20 · Answer 9 · answered Feb 27 '13 at 11:26

20

In Activity on click of button showing a dialog box

Dialog dialog = new Dialog(MyActivity.this);

Worked for me.

answered Feb 27 '13 at 11:26

P_Pran

211
2
6

Mikalai Daronin · Answer 10 · 2019-01-08T10:19:05.077

18

Little hack: you can prevent destroying your activity by GC (you should not do it, but it can help in some situations. Don't forget to set contextForDialog to null when it's no longer needed):

public class PostActivity extends Activity  {
    ...
    private Context contextForDialog = null;
    ...
    public void onCreate(Bundle savedInstanceState) {
        ...
        contextForDialog = this;
    }
    ...
    private void showAnimatedDialog() {
        mSpinner = new Dialog(contextForDialog);
        mSpinner.setContentView(new MySpinner(contextForDialog));
        mSpinner.show();
    }
    ...
}

edited Jan 08 '19 at 10:19

answered Dec 03 '12 at 10:03

Mikalai Daronin

8,590
2
35
47

@MurtuzaKabul It works because this == PostActivity which inherits from Activity-> which inherits from Context, so when you pass the dialog your context you are actually passing the activity – Elad Gelman Jul 25 '13 at 15:26

score 18 · Answer 11 · edited Aug 04 '23 at 23:56

Just use following:

FOR JAVA USERS

In case you are using activity --> AlertDialog.Builder builder = new AlertDialog.Builder(this);

OR

AlertDialog.Builder builder = new AlertDialog.Builder(your_activity.this);

In case you are using fragment --> AlertDialog.Builder builder = new AlertDialog.Builder(requireActivity());

FOR KOTLIN USERS

In case you are using activity --> val builder = AlertDialog.Builder(this)

OR

val builder = AlertDialog.Builder(this@your_activity)

In case you are using fragment --> val builder = AlertDialog.Builder(requireActivity())

score 13 · Answer 12 · answered Nov 23 '13 at 15:43

If you are using a fragment and using AlertDialog/Toast message then use getActivity() in the context parameter.

like this

ProgressDialog pdialog;
pdialog = new ProgressDialog(getActivity());
pdialog.setCancelable(true);
pdialog.setMessage("Loading ....");
pdialog.show();

score 9 · Answer 13 · edited May 19 '16 at 21:57

9

adding

dialog.getWindow().setType(WindowManager.LayoutParams.TYPE_SYSTEM_ALERT);

and

"android.permission.SYSTEM_ALERT_WINDOW"/> in manifest

It works for me now. After even close and open the application, gave me the error at that time.

edited May 19 '16 at 21:57

Jorgesys

124,308
23
334
268

answered Apr 21 '15 at 11:06

AlphaStack

125
1
6

score 9 · Answer 14 · answered Nov 04 '16 at 14:18

I was using ProgressDialog in a fragment and was getting this error on passing getActivity().getApplicationContext() as the constructor parameter. Changing it to getActivity().getBaseContext() didn't work either.

The solution that worked for me was to pass getActivity(); i.e.

progressDialog = new ProgressDialog(getActivity());

MSA · Answer 15 · 2014-01-06T10:37:39.447

6

Use MyDialog md = new MyDialog(MyActivity.this.getParent());

edited Jan 06 '14 at 10:37

answered May 01 '13 at 07:42

MSA

2,502
2
22
35

score 6 · Answer 16 · answered Jul 01 '14 at 22:29

If you are outside of the Activity then you need to use in your function "NameOfMyActivity.this" as Activity activity, example:

public static void showDialog(Activity activity) {
        AlertDialog.Builder builder = new AlertDialog.Builder(activity);
        builder.setMessage("Your Message")
        .setPositiveButton("Yes", dialogClickListener)
        .setNegativeButton("No", dialogClickListener).show();
}


//Outside your Activity
showDialog(NameOfMyActivity.this);

score 5 · Answer 17 · answered Jan 12 '13 at 04:05

5

If you are using a fragment and using an AlertDialog / Toast message, use getActivity() in the context parameter.

Worked for me.

Cheers!

answered Jan 12 '13 at 04:05

curlyreggie

1,530
4
21
31

score 5 · Answer 18 · answered Aug 22 '13 at 08:33

Try to use the context of an activity which will be under the dialog. But be carefull when you use "this" keyword, because it will not work everytime.

Forexample, if you have TabActivity as host with two tabs, and each tab is another activity, and if you try to create dialog from one of the tabs (activities) and if you use "this", then you will get exception, In this case dialog should be connected to host activity which host everything and visible. (you can say most visible parent Activity's context)

I did not find this info from any document but by trying. This is my solution without strong background, If anybody with better knownledge, feel free to comment.

score 5 · Answer 19 · answered Sep 20 '16 at 14:36

For future readers, this should help:

public void show() {
    if(mContext instanceof Activity) {
        Activity activity = (Activity) mContext;
        if (!activity.isFinishing() && !activity.isDestroyed()) {
            dialog.show();
        }
    }
}

score 3 · Answer 20 · edited Oct 13 '18 at 09:01

3

Try getParent() at the argument place of context like new AlertDialog.Builder(getParent()); Hope it will work, it worked for me.

edited Oct 13 '18 at 09:01

Hossein Golshani

1,847
5
16
27

answered Feb 05 '13 at 07:27

Priyank Joshi

151
1
4

score 2 · Answer 21 · answered Nov 29 '12 at 12:07

2

In my case work:

this.getContext();

answered Nov 29 '12 at 12:07

theWalker

2,022
2
18
27

score 2 · Answer 22 · edited Oct 13 '18 at 08:55

2

I think it may happen as well if you are trying to show a dialog from a thread which is not the main UI thread.

Use runOnUiThread() in that case.

edited Oct 13 '18 at 08:55

Hossein Golshani

1,847
5
16
27

answered Apr 17 '13 at 09:28

Erwan

3,733
30
25

score 2 · Answer 23 · answered Dec 01 '15 at 07:11

2

Or another possibility is to create Dialog as follow:

final Dialog dialog = new Dialog(new ContextThemeWrapper(
            this, R.style.MyThemeDialog));

answered Dec 01 '15 at 07:11

Martin Koubek

433
4
8

score 1 · Answer 24 · answered Dec 16 '14 at 13:27

After taking a look at the API, you can pass the dialog your activity or getActivity if you're in a fragment, then forcefully clean it up with dialog.dismiss() in the return methods to prevent leaks.

Though it is not explicitly stated anywhere I know, it seems you are passed back the dialog in the OnClickHandlers just to do this.

score 1 · Answer 25 · answered Aug 14 '19 at 23:53

If your Dialog is creating on the adapter:

Pass the Activity to the Adapter Constructor:

adapter = new MyAdapter(getActivity(),data);

Receive on the Adapter:

 public MyAdapter(Activity activity, List<Data> dataList){
       this.activity = activity;
    }

Now you can use on your Builder

            AlertDialog.Builder alert = new AlertDialog.Builder(activity);

score 1 · Answer 26 · answered Jun 17 '20 at 07:37

Guys I got a simple cheat sheet. create a file give it any name then in it write this code

fun Context.alertdialog(context: Context, msg: String, icon: Drawable, title:String){
    val alertDialog = AlertDialog.Builder(context)
    alertDialog.setIcon(icon)
        .setTitle(title)
        .setMessage(msg)
    alertDialog.show()
}

now when you need to show an alert dialog only use this method anywhere

requireActivity().alertdialog(requireContext(), resources.getString(R.string.pass_title),
                resources.getDrawable(R.drawable.pass_ic_name), "title")

Goodluck for Kotlin

score 1 · Answer 27 · answered Aug 28 '20 at 13:41

What worked for me was to pass the activity instead of the context.

I wanted a custom layout for my dialog, but to keep my code separate, I created it in a separate Class, else I would have to copy and paste that chunk of code into every activity where I want to use the dialog.

Solution explains my situation but it gives the core solution:

As I was using a ViewAdapter I initialised the adapter with the Activity (not context ex. ->[kotlin] activity: Activity) as a parameter -> ex. [kotlin] this@MainActivity
Then I passed that parameter to the Viewholder
After which passing it again to the class that will inflate the Dialog.

Use the activity[optional name]: Activity[mandatory type] every where until it gets to the dialog you want to inflate

Its a lot of passing around, but it does make more sense over copy and pasting the same code everywhere

score 0 · Answer 28 · answered Aug 05 '19 at 22:33

Here is how I resolved same error for my application:
Adding the following line after creating the dialog:

dialog.getWindow().setType(WindowManager.LayoutParams.TYPE_SYSTEM_DIALOG);

You will not need to acquire a context. This is particularly useful if you are popping up another dialog over current popped up dialog. Or when it's not convenient to get a context.

Hope this can help you with your app development.

David

Dialog throwing "Unable to add window — token null is not for an application” with getApplication() as context

28 Answers28

* kotlin version *

Linked

Related

Dialog throwing "Unable to add window — token null is not for an application” with getApplication() as context

28 Answers28

***** kotlin version *****

Linked

Related

* kotlin version *