App does not start with last used note opened, instead it opens first node in that notebook.

[selivan]

Operating system

Windows

Joplin version

3.0.13

Desktop version info

Joplin 3.0.13 (prod, win32)

Client ID: 3c3b2cb8e2194f7791b36b2260e2fae2
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 599cf5b

Backup: 1.4.1
Conflict Resolution: 1.2.3
Copy Code Blocks: 1.1.1
Note list and sidebar toggle buttons: 1.0.3

Current behaviour

1. Open some notebook with more than 1 note
2. Select any note other than first in selected sort order
3. Close Joplin
4. Open Joplin
5. Now the first(according to selected sort order) note is opened, not the note that was opened last time

I tried disabling all installed plugins, it didn't help.

Expected behaviour

After re-opening the application exactly the same note should be selected.

NOTE: opening last used note worked fine while I was using Joplin 2. This started after upgrading to version 3, including latest 3.13 release.

[selivan]

Updated to Joplin 3.0.14, the bug still exists.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[selivan]

@github-actions This issue hasn't been fixed.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[selivan]

Nope, the issue is still not fixed in Joplin 3.0.15.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[selivan]

Nope, the issue is still not fixed in Joplin 3.0.20. And the github bot is the only one who cares.

Hey, Joplin guys, I even bought the cloud to support development. Maybe look into this?

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

[selivan]

This issue is not closed. Prolonged period of inactivity is due to nobody fixing this.

The issue is still here for Joplin Joplin 3.1.24

[selivan]

Opened new issue for this bug: #11484