Lol. Oh I remember being your level of optimistic about android, that passed about 5 years ago...

Read the android docs and you will quickly discover that it's all bs, they have fat warnings everywhere saying that they may not happen.

The android life cycle is a great idea, but they didn't implement it probably. Now it's garbage. Basically I have seen most parts skipped, or called twice, or called out of order (when there is more than one activity) 🤦

There are different ways to deal with this, mine was to not trust all the life cycle calls, and feed them into my own generic handler of state, then that keeps track of It's own state and calls my own start or stop functions. This then debounces and allows android to forget to call things.

At the very minimum you need to combine onPause and onStop (and maybe onSaveInstanceState() ) to get anything reliable.

autosave not persistant #234

Description

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions