Pass Application Context to the view instead of Activity Context

Question

Why use Activity Context while we can use Application Context to load and access resource? Means if I use Application Context instead of Activity Context there is no Exception occur so why use Activity Context?

Example:

In below example if I use getApplicationContext() instead of "this" pointer inside the Activities onCreate() it works fine without any exception.

 Button button = new Button(getApplicationContext());

Check this related question http://stackoverflow.com/a/987503/1705641 — Evos, Dec 29 '12 at 07:37

score 2 · Accepted Answer · answered Dec 29 '12 at 07:50

getApplicationContext() should be used with the view, which will be having scope outside the Activity (An example of it might be when you bind to a Service from an Activity).

But for Defining Views like as you mentioned above (to define a Button), you should Definitely use Activity's Context (MyActivity.this or Simply this).

The reason for it is if you use getApplicationContext(), it will live as longer as the Whole Application lives. But for a Button, it should destroy as soon the Activity finishes, So it is always better to use this(Activity's Context), when defining such type of Views.

if I use Application Context instead of Activity Context there is no Exception

There is no exception because both are valid Contexts. Its upon you that if you keep your view alive for entire application lifetime, even if it is not needed (which would ultimately lead to Memory Leakages), or you want to destroy it with as soon as the Activity finishes.

I don't see how passing app context into view's constructor will extend it's lifetime beyond activity. The view is holding onto the app context reference and not the other way round, so as soon as the inflated layout, which is holding said view, is destroyed, the view should also be ready for GC unless you have another handle to it. — AAryz, Jun 11 '18 at 10:18

score 0 · Answer 2 · answered Dec 29 '12 at 07:42

They are both instances of Context, but the application instance is tied to the lifecycle of the application, while the Activity instance is tied to the lifecycle of an Activity. Thus, they have access to different information about the application environment.

If you read the docs at getApplicationContext it notes that you should only use this if you need a context whose lifecycle is separate from the current context. This doesn't apply in either of your examples.

The Activity context presumably has some information about the current activity that is necessary to complete those calls. If you show the exact error message, might be able to point to what exactly it needs.

But in general, use the activity context unless you have a good reason not to.

Pass Application Context to the view instead of Activity Context

2 Answers2

Linked