Gracefully handle IntegrityError on FCMDeviceAuthorizedViewSet about fcm-django HOT 7 CLOSED

Why is it even possible to change the id field? Is there a use-case for that?

from fcm-django.

So far as I can tell, it should not be possible to change the primary key of the record, at all. If the primary key was the registration_id, it would make sense to allow modification of it, but it is not.

You could submit a PR that makes the autoincrement id read_only, and hopefully, this projects maintainer would accept it. Or explain why changing the id is needed, if not.

from fcm-django.

This project is in desperate need of maintainers as I am very short on time. But I will do my best to review.

from fcm-django.

Be more specific. Request where and what is the error returned with DEBUG = True

from fcm-django.

Error:

duplicate key value violates unique constraint "fcm_django_fcmdevice_pkey" DETAIL: Key (id)=(1) already exists.

upon having a duplicate key it should result in a 400 error with a meaningful message so that frontend developers can work with it, Right now it's just creating an error 500.

from fcm-django.

Alright, I will submit a PR and hopefully, it will get approved.

from fcm-django.

Fix merged in #72

from fcm-django.