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

Imported form file, cannot create API key [API v2 QA] #4746

Open
anikbrazeau opened this issue Nov 29, 2024 · 2 comments
Open

Imported form file, cannot create API key [API v2 QA] #4746

anikbrazeau opened this issue Nov 29, 2024 · 2 comments
Labels
App bug Something isn't working

Comments

@anikbrazeau
Copy link
Member

anikbrazeau commented Nov 29, 2024

Description

Opening a form file that was saved to computer does not allow me to create an API key for unknown reason:
The API key could not be created
There was an error creating the API key. Please try again later.

Does this have to do with the saving bug when a form file is imported? (See #4111 #4079 #3628)

Steps to reproduce

  1. Go to GC Forms
  2. Create a new form
  3. Open form file
  4. Select API delivery in Settings
  5. Create API key
  6. Type AGREE and continue
  7. See error

Details

  • Browser: Chrome
  • Operating system: Mac
  • Environment: Staging
  • Language: EN
  • Viewport: Desktop

Expected behaviour

Clearer indication of what happened or what to do?

Screenshots or videos

Screenshot 2024-11-29 at 9.51.48 AM.png

@anikbrazeau anikbrazeau added App bug Something isn't working labels Nov 29, 2024
@Abi-Nada
Copy link

Abi-Nada commented Dec 2, 2024

@anikbrazeau can you confirm if the form had an ID in the URL before updating the Settings? (//do you know if the form file was saved before updating settings? If not, it's most likely related to #3628)

@anikbrazeau
Copy link
Member Author

anikbrazeau commented Dec 2, 2024

You're right on, the form did not have an ID/name.
https://forms-staging.cdssandbox.xyz/en/form-builder/0000/publish
https://forms-staging.cdssandbox.xyz/en/form-builder/0000/settings

However, this is not expected as a user, and the error message does not indicate how to correct the problem. Is there a way we could ensure a form ID is created on import to avoid this issue?

Screenshot 2024-12-02 at 9 09 48 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants