This action generate this error:
Hi Saber , could you please share what error you are facing and whats your motive as well, that will help us to portrait the issue.
Many thanks.
I’m working with the free plan of apidog to build a rest api specification.
Since 2 days I published a new version 1.0.0 forked from “main” and it worked fine. Yesterday there was an update on the main version and I tried to publish it on the version 1.0.0 which is already published, but since I’m using the free plan I had to remove the current version and created again a new one with the same tag 1.0.0. At this stage when I checked the published spec (https://masarat.apidog.io/) I noted that was not found (message: This documentation does not exist or has been deleted).
Now, when I go to the publish section to re-check the issue in Admin side, I got the error above (screenshots).
Hi Saber , Thank you for sharing your detailed findings with us! We appreciate the time you’ve taken to bring this to our attention.
I’m glad to let you know that we’ve successfully reproduced the issue, and it has already been logged for resolution. Our development team is actively working on a fix, which will be included in an upcoming version of Apidog.
We truly appreciate your patience and understanding as we work to address this. Stay tuned for updates, and feel free to reach out if you have any additional questions or need further assistance in the meantime!
Thank you for your feedback. Once fixed, how many time is needed to be ready in production?
Hi Saber , our updates on Apidog follows a standard pipeline to release versions fixing issues and also introducing new features within it. It has been already logged to be fixed, and I can assure you it will be fixed soon.
Thanks for your kind understanding.
Thanks
Hi Saber , Good day. I want you to know that the issue has been fixed and could you please check it on your end and let me know? I will be waiting for your confirmation.
Once again, thanks for choosing Apidog.
Good morning Md Mamunur Rashid, thank you for the feedback.
Yesterday, we have found a workaround (project re-creation) to resolve the issue for our user. Then to prevent the bug happen again we make sure that we switch the published spec to the “main” before delete / re-create version.
Unfortunately, w cannot today simulate to reproduce the bug to not distrub the user, but this will be possible in the next days.
Saber , thanks for your response. Have a good day.