Is it possible for the onDestroy method to be called without a prior call to onStop?

Yes, such a situation is possible, although rare. In the lifecycle of an Android Activity, the onStop method is called when the activity is no longer visible, and onDestroy is called when the activity is destroyed.

However, if the system decides to destroy the activity immediately (for example, due to low memory or when calling finish()), onDestroy may be called without a prior onStop.

Example:

• The activity is on the screen.
• The user calls finish(), and the system immediately destroys the activity.

In this case, onStop may not be called, but onDestroy will be called directly.

Therefore, when implementing logic, it is important to consider that onDestroy can be called without onStop.