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

Card can be added multiple times on the same device #1850

Open
seluianova opened this issue Jan 7, 2025 · 2 comments · May be fixed by #1876
Open

Card can be added multiple times on the same device #1850

seluianova opened this issue Jan 7, 2025 · 2 comments · May be fixed by #1876
Assignees
Labels
Bug Something isn't working

Comments

@seluianova
Copy link
Contributor

seluianova commented Jan 7, 2025

Describe the bug
If the user scans the QR code of a card that has already been added to the device, the user will receive the message "Your card has already been activated on another device. If you continue, your card will be automatically deactivated on the other device if it is still active there."
If the user proceeds, he gets the same card 2 times on the same device (first one is revoked, second one is active).

To Reproduce
The issue can be reproduced for projects that allow more than 1 card (Nürnberg, Koblenz)
Steps to reproduce the behavior:

  1. Create PDF for the card activation
  2. Open the app --> Ausweisen --> Pass aktivieren
  3. Scan the QR code
  4. When the card is added, scan the same code again.

Expected behavior
I think there should be the message "This card has already been activated on this device"

@seluianova seluianova added the Bug Something isn't working label Jan 7, 2025
@f1sh1918
Copy link
Contributor

f1sh1918 commented Jan 8, 2025

good find. i think currently we only check this for deeplink activation

@seluianova
Copy link
Contributor Author

@f1sh1918

i think currently we only check this for deeplink activation

actually it seems to be broken by this change #1721

@seluianova seluianova moved this to Next Up in team-app Jan 8, 2025
@f1sh1918 f1sh1918 assigned f1sh1918 and unassigned f1sh1918 Jan 15, 2025
@f1sh1918 f1sh1918 moved this from Next Up to In Progress in team-app Jan 21, 2025
@f1sh1918 f1sh1918 linked a pull request Jan 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants