Current Status: Resolved (status.quickbox.io)
An issue with the Lifetime API endpoint has been brought to my attention. This issue only affects Lifetime API keys. After a lengthy update to the API management system, it would appear that a bug has been introduced that is resetting non-renewable API resources every 24 to 48 hours. I apologize for the annoyance this may bring some of our lifetime holders. Do keep in mind that this will not interfere with the typical daily workings of your applications installed. You can still use them and update them internally (should the application provide an internal updating mechanism of its own).
Update: May 18, 2023
Happy to report the issue has now been resolved. All API endpoints have been restored and can now be reactivated. Thanks again for everyone’s patience through this bug, be on the lookout for a release this weekend!
Update: May 16, 2023
I am hoping to have this issue fully resolved within the next couple of days for the Lifetime endpoints and their associated resources resetting. In additional testing and verification, it looks as though the expiration bug is a bit deeper than the logic itself. The source of the bug, I don’t want to make promises but this appears to be the culprit, is an underlying issue on the resource cleaning mechanism itself. This is under continued investigation and I will post back another update as I have it.
Update: May 14, 2023
After many hours of review and testing, we’ve narrowed down the bug!
There was a logic bug in is_time_expired(). This was causing API Subscriptions with an access expiration of zero value, meaning infinite/lifetime, to be deleted during cleanup. Cleanup being the process where our API management system removes outdated/expired keys from the system. The bug essentially saw lifetime endpoints as expired and thusly removed them. I still have this under a watchful eye as this bug in particular has been resolved, but it’s best to be absolutely certain before marking this as fully resolved; it was a rather large update to our systems, so best to be safe.
I will begin slowly reactivating lifetime api keys and should have everyone back and activated here in the next couple of days. This is only to ensure that the bug has been fully squashed. Once all lifetime members and their keys are re-assigned, I will push out the next release of QuickBox Pro v3.
Thank you again for everyone’s ongoing patience in this matter. Bugs are not something we plan for and all we can do is pour everything we have into resolving them once they do occur… and of course, some patience. 💖
Update: May 13, 2023
The investigation of the issue with Lifetime API endpoints is still ongoing. The issue seems to arise from a threshold event (once a certain number of resources are used, the keys reset/clear out). As I continue to work on this and narrow down the issue at hand, I will continue activating accounts that request their keys be re-activated. This in no way affects your payments or your status with the keys. The squashing of this issue is underway and I will post back additional updates as I have them. Thank you again for your patience and your continued understanding, I know this is annoying and incredibly inconvenient.
Original Post: May 11, 2023
As I continue to investigate this issue, Lifetime holders may receive emails informing them of their newly generated API keys. These will appear as order details to their given email inbox, these are not charges, they are simply being issued with the new keys as is designed by the system we use.
I will be enabling and resetting current Lifetime API endpoints (slowly) over the next 48 hours. This is to ensure that no stone is left unturned in the testing and tracking down of the bug in question, we have to test all the variables. If it is imperative that you have your API reset within this time, please open a support ticket and let us know, we’ll get it reset for you ASAP! Please keep in mind that they could potentially reset once more during the testing phases.
Again, I offer my sincerest apologies for this annoyance, but rest assured, I am working on this closely and am hoping to have this resolved within the next couple of days. I will update this post just as soon as I have a resolution in place. Thank you for your patience and understanding.