You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UPDATE: Sorry - just read the README.md in the app. Please feel free to delete my issue as I see you have raised that you've had issues with Flask-Session.
Hi. Running this app and the starter app results in the error "'Flask' object has no attribute 'session_cookie_name'". Details of the issue and the solution can be found at https://stackoverflow.com/questions/76139355/flask-object-has-no-attribute-session-cookie-name - I have implemented this solution and it works. In short, the issue is Flask >= 2.3.1 removed those names and a solution can either be to wind back the version of Flask or update the version of Flash-Session. Personally I prefer the latter - as of the date of raising this issue, this app's requirements.txt fixes the Flask-Session at 0.3.2 but does not set a fixed Flask version. So Flask is bang up to date but Flask-Session is not, causing the issue.
The text was updated successfully, but these errors were encountered:
UPDATE: Sorry - just read the README.md in the app. Please feel free to delete my issue as I see you have raised that you've had issues with Flask-Session.
Hi. Running this app and the starter app results in the error "'Flask' object has no attribute 'session_cookie_name'". Details of the issue and the solution can be found at https://stackoverflow.com/questions/76139355/flask-object-has-no-attribute-session-cookie-name - I have implemented this solution and it works. In short, the issue is Flask >= 2.3.1 removed those names and a solution can either be to wind back the version of Flask or update the version of Flash-Session. Personally I prefer the latter - as of the date of raising this issue, this app's requirements.txt fixes the Flask-Session at 0.3.2 but does not set a fixed Flask version. So Flask is bang up to date but Flask-Session is not, causing the issue.
The text was updated successfully, but these errors were encountered: