Facebook login failed after the update



  • Hi, I've updated Spotipo from 3.18 to 3.2 and now have an issue regards to facebook login.
    When I'm choosing the option to ask for like I get the internal 500 error.
    If I turn down this like demand everything working fine.

    Here is the logs:
    Traceback (most recent call last):
    File "/usr/share/nginx/spotipo/.env/local/lib/python2.7/site-packages/flask/app.py", line 2292, in wsgi_app
    response = self.full_dispatch_request()
    File "/usr/share/nginx/spotipo/.env/local/lib/python2.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
    rv = self.handle_user_exception(e)
    File "/usr/share/nginx/spotipo/.env/local/lib/python2.7/site-packages/flask/app.py", line 1718, in handle_user_exception
    reraise(exc_type, exc_value, tb)
    File "/usr/share/nginx/spotipo/.env/local/lib/python2.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
    rv = self.dispatch_request()
    File "/usr/share/nginx/spotipo/.env/local/lib/python2.7/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.view_functionsrule.endpoint
    File "spotipo/unifispot/core/guestutils.pyx", line 123, in unifispot.core.guestutils.validate_track.decorated_function
    File "spotipo/unifispot/modules/facebook/main.pyx", line 151, in unifispot.modules.facebook.main.validate_fbconfig.decorated_function
    File "spotipo/unifispot/core/guestutils.pyx", line 538, in unifispot.core.guestutils.get_loginauth_validator.validate_loginauth.decorated_function
    File "spotipo/unifispot/modules/facebook/main.pyx", line 368, in unifispot.modules.facebook.main.fb_like
    File "spotipo/unifispot/core/utils.pyx", line 337, in unifispot.core.utils.render_guest_template
    AttributeError: 'NoneType' object has no attribute 'template_type'
    [pid: 8395|app: 0|req: 95/197] 10.71.72.18 () {48 vars in 1568 bytes} [Mon Feb 4 10:21:05 2019] GET /fb/like/0ea6a02a-3cd7-4b51-8da5-39cb8f6aed11 => generated 2260 bytes in 38 msecs (HTTP/$



  • @Dmitrij-Bezruchko

    Thanks for reporting,

    Could you please upgrade to 3.2.5, it should fix this issue


Log in to reply
 

});