no such table: main.socialaccount_socialapp__old

[aellerton]

no such table: main.socialaccount_socialapp__old

[aellerton]

Hey, Thanks for the nice words. Can you list the exact steps you followed please...

…

On Tue., 9 Apr. 2019, 19:45 berat703, ***@***.***> wrote: Hey! First of all thanks for this repository.I did all steps successfully but I got an error when I run python manage.py set_auth_provider google GOOGLE_CLIENT_ID GOOGLE_SECRET_ID and the error is django.db.utils.OperationalError: no such table: main.socialaccount_socialapp__old Database created successfully with 'manage.py migrate' — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#20>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7EolXKSbP-iW-HJc8bfOHNqVz-xSCfks5vfH1TgaJpZM4ckS5T> .

[beratn]

I did same steps that you wrote on readme.

`
$ cd demo-allauth-bootstrap
$ python3 -m venv mypy # you can call it anything, not just "mypy"
$ . mypy/bin/activate
$ pip install -r requirements.txt
$ python configure.py
$ python manage.py makemigrations allauthdemo_auth
$ python manage.py migrate
$ python manage.py createsuperuser
$ python manage.py set_auth_provider google GOOGLE_CLIENT_ID GOOGLE_SECRET_ID // this is error step
.
.
.

`

[aellerton]

Googling for "no such table main.auth_user__old" finds this:

https://stackoverflow.com/questions/53637182/django-no-such-table-main-auth-user-old

which is an SQLite issue. The same thread describes that Django 2.1.5 fixes it,
so I upgraded to that version and the latest allauth.

After this, the usual setup steps worked for me.