Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REGRESSION: forced to recompile all server parameters if certificate is changed #8308

Closed
2 tasks done
Ivan-SB opened this issue Oct 10, 2024 · 1 comment
Closed
2 tasks done
Labels
type: bug Something is causing incorrect behavior or errors unconfirmed Newly reported issues awaiting triage or confirmation

Comments

@Ivan-SB
Copy link

Ivan-SB commented Oct 10, 2024

Checklist

  • I have used the search function to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.

App version

8.0b2

Where did you get the app from?

Google Play

Android version

14

Device model

Samsung Galaxy A33 5G

Steps to reproduce

When a certificate was expiring or simply was changed (certibot/let's encrypt) I was used to go to account setting -> Fetching mail -> Incoming server and simply chose Next (or whatever there was before, I can't check since now it is different) and accept the new certificate.
Same for outgoing email.
Now whenever I go to setting it starts by requiring again the email and make me compile ALL the fields again.

I don't know if this just happens if certificates are expired... or every time you try to change something in the server configuration, but that's very inconvenient.

BTW once there I couldn't find anymore the "Push" settings. It is not clear if it automatically default to Push or it doesn't support Push anymore and now the only option is pooling emails.

thanks

Expected behavior

a) see the form as it was before
b) provide the choice between wizard (?) and manual setup remembering previous setup

Actual behavior

REDO all settings

Logs

No response

@Ivan-SB Ivan-SB added type: bug Something is causing incorrect behavior or errors unconfirmed Newly reported issues awaiting triage or confirmation labels Oct 10, 2024
@cketti
Copy link
Member

cketti commented Oct 10, 2024

This is a bug in the navigation. It'll be fixed in 8.0b3.

Duplicate of #8271

@cketti cketti closed this as completed Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something is causing incorrect behavior or errors unconfirmed Newly reported issues awaiting triage or confirmation
Projects
None yet
Development

No branches or pull requests

2 participants