Uniqkey incident
[Legacy] Temporary Issue in UniqKey Legacy App 1.0: Inability to open mobile app
Uniqkey experienced a minor incident on August 14, 2024 affecting [Legacy] Uniqkey Mobile APP, lasting 15d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 14, 2024, 06:32 AM UTC
Incident Details: We are currently experiencing an issue in the UniqKey Legacy App where it is not possible to open the mobile app. Timeframe: - Start Time: 14/8/2024, 8:11 UTC+2 ETA: We expect to have this issue resolved within today. Our team is working diligently to ensure a swift resolution, and we appreciate your patience. We will post updates in this thread. What is affected: Please note that only the mobile app is affected by this issue. Our team is working diligently to resolve the problem, and we appreciate your patience. Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected]
- identified Aug 14, 2024, 06:36 AM UTC
The issue has been identified as specific to our newest Android build, 3.7.0. If you are currently using version 3.6.5, please do not update to the latest version. A fix is currently in development.
- identified Aug 14, 2024, 01:02 PM UTC
We have made a new build that is currently being sent for review and will be published as soon as possible for our Uniqkey Legacy customers. However, we want to inform you that this build has two known issues: 1. You cannot create secure notes. You can still use existing secure notes. 2. You cannot create credit cards. You can still use existing credit cards. Despite these bugs, we have decided to push the build to resolve the issue promptly. Our team will be working on fixing these two bugs over the next several days. ETA: The updated app should be live for everyone within the next few hours. We appreciate your patience as we work through these remaining issues.
- identified Aug 19, 2024, 07:26 AM UTC
We wanted to provide a quick update on the current situation with the Uniqkey Legacy App. Our team is still actively investigating the issue that has been affecting our latest Android build (version 3.7.0). At this time, we are observing degraded performance, which means the mobile app may take longer than usual to process requests. In addition to this, we have identified a new issue related to our backend infrastructure. This new issue may further impact the performance and stability of the mobile app. Our team is now working on both the original issue with the Android build and this newly identified backend issue. We understand that these issues are causing inconvenience, and we apologize for the disruption. Please rest assured that our team is working diligently to identify the root causes and implement solutions as quickly as possible. Next Steps: - We are continuing to investigate the causes of these performance issues. - A fix for both the Android build issue and the backend issue is actively being developed and will be released as soon as it is thoroughly tested. ETA: We do not have a definitive timeline for resolution but will provide updates as more information becomes available. Thank you for your continued patience and understanding. If you have any questions or require further assistance, please contact our support team at [email protected].
- monitoring Aug 19, 2024, 02:39 PM UTC
We are pleased to inform you that the Uniqkey Legacy App is now fully operational. The issues affecting secure notes and credit cards have been successfully resolved, and the app is no longer experiencing degraded performance. However, we want to highlight a couple of minor issues that we are still addressing: - Trusted Browser: The Trusted Browser feature is not functioning properly with single requests. Our team is actively working on a fix for this. - Autofill on Android 14: Autofill functionality is currently not working on devices running Android 14. We are investigating this issue and will provide a resolution as soon as possible. We would also like to emphasize that these issues are specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected. We appreciate your patience as we continue to fine-tune the Legacy app and address these remaining issues. In the coming days, we will be closely monitoring our Legacy platform to ensure it remains fully operational. If you encounter any other problems or need assistance, please reach out to our support team at [email protected]. Thank you for your continued support.
- monitoring Aug 21, 2024, 07:57 AM UTC
We are currently investigating and monitoring an issue reported by multiple users where the login process stalls after approving the login prompt in the mobile app. This issue primarily affects users on Edge and Firefox browsers, though some reports suggest it may also affect Chrome. Note: We would also like to emphasize that these issues are specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected.
- monitoring Aug 21, 2024, 08:09 AM UTC
The issue causing the login process to stall after the login prompt is approved in the mobile app, will be filed as a seperate incident. We are doing this to ensure that it is tracked independently of any other ongoing issues. Previous update - August 19th 2024, 16:39 CEST - is still the current status. Note: We would also like to emphasize that these issues are specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected.
- monitoring Aug 22, 2024, 12:36 PM UTC
Update: We are currently working on the following issues affecting the Uniqkey Legacy App: 1. Secure Notes Visibility: Issue: Secure notes within groups are currently not visible in the mobile app. Workaround: These notes are still accessible through the Uniqkey browser extension. Please use the extension to view or edit group secure notes for now until we have fixed this issue. 2. Autofill on Android 14: Issue: Autofill functionality remains non-operational on devices running Android 14. Update: Our team is actively investigating this issue, and we will provide a fix as soon as possible. 3. Private Secure Notes Editing: Issue: Attempting to edit a private secure note in the app redirects users to the “create new credit card” screen. Workaround: Editing private secure notes is still possible through our browser extension. Next Steps: We are continuing to monitor the situation closely and are working on resolving these issues. Updates will be provided as progress is made. Note: We would also like to emphasize that these issues are specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected. Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected]
- resolved Aug 29, 2024, 11:20 AM UTC
The incident is now officially closed, and the UniqKey Legacy App is operational as of August 19th 2024, 16:39 CEST. However, the minor issues mentioned in the previous update may still persist. Please note, these issues are specific to the Legacy platform and do not affect the UniqKey 2.0 platform: 1. Secure Notes Visibility: Notes within groups are still not visible in the mobile app. 2. Autofill on Android 14: Autofill functionality is non-operational on Android 14 devices. 3. Private Secure Notes Editing: Editing private secure notes redirects to the “create new credit card” screen. For further updates on these issues, please contact [email protected]