Getting resources when fragment is no longer attached

Question

What's the recommended way of accessing app's resources in a situation where the fragment may or may not be attached to the activity?

The reason I'm asking it's causing crashes when the asynchronous bit of code is getting executed while, for a reason like sending app to background, the fragment is no longer attached.

I could check if the fragment isAdded() and cancel the whole thing if it's not. But I'm thinking - can I just use app context reference kept in my Application? This should still be valid, correct?

Is accessing resources MyApplication.getContext().getResources() recommended approach or it has downsides?

Thanks

I think you will face memory leak issues – Mohammad Rahchamani Feb 11 '16 at 10:19 — Mohammad Rahchamani, Feb 11 '16 at 10:19

score 1 · Answer 1 · answered Feb 11 '16 at 10:17

1

You should take a class extending Application and make it singleton. Then from anywhere in your code, you can call getResources() on this application instance. And this is a correct approach.

answered Feb 11 '16 at 10:17

Anish Mittal

1,157
12
29

That's what I'm doing where context is not directly available. Thanks Anish. – wtk Feb 12 '16 at 11:40

Getting resources when fragment is no longer attached

1 Answers1