-
Notifications
You must be signed in to change notification settings - Fork 247
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
Amplify Fails to Configure - "WorkerBeeExceptionImpl" #4161
Comments
@BeamTrakLLC Was this a fresh install on a new computer, or one that had previously been running the application without issue? |
This computer had been running previous versions without any issues. We then tried removing the application entirely and installing a previous working version. The error still occurs though. |
Hi @BeamTrakLLC, I installed a sample app with auth and storage on windows and also ran the application from an MSIX installer and was not able to reproduce the issue. Due to this problem only happening on one computer and the workerbee error showing |
Thank you for your help @khatruong2009, a corrupt file is definitely a possibility. We ran "SFC /scannow" in hopes of the error being related to a corrupt OS file but it did not fix the issue. The only outlier we can think of in regards to how the program was installed on the computer is when installing the certificate for the MSIX installer. The computer was in the incorrect timezone when we installed the certificate which caused this error:
This was resolved by changing the computer to the correct timezone and soon after the application was moved to have a launcher to handle updating and launching the app. But recently we moved back to a standard MSIX installer to allow for in-place updates and remove the need to bug test both the application and launcher. This issue seems to be different though considering the previous certificate error would still allow amplify to configure and would only occur when the user attempted to login. We are going to get the current version of the app to work with the previous launcher to see if that allows amplify to configure. If that is the case then we know the issue is within the changes made between those updates. We will report back Monday Nov 27th as the office is closed for the holidays after today. |
We switched the program back to the previously working launcher. This did not fix the issue and upon further testing this change worked on every other computer except the problem computer. We think this issue is deeper than the program as other issues began to arise on the problem computer. Things such as the search bar not opening, file explorer randomly closing, and applications being unable to uninstall and reinstall. |
Hi @BeamTrakLLC, sounds like this issue is related to that one specific computer. I'm going to close this issue but feel free to let us know if another issue comes up. |
Description
We have a Flutter desktop application that implements Amplify Auth and S3 Storage. We distribute the application via MSIX installer. There has been no issues distributing and running the application until last week on one computer. The computer would not load the Authenticator widget as amplify would not configure correctly. Unable to recreate the issue on different computers, we installed the development tools on the problem computer and were given the following error:
We tried pulling the amplify environment, reconfiguring the environment, and even deploying a test amplify environment. All attempts ran into the same issue. Below is a code snippet of what is being run and where it fails:
Any help would be greatly appreciated. Below is the flutter doctor from the computer with the issue:
Categories
Steps to Reproduce
No response
Screenshots
No response
Platforms
Flutter Version
3.13.9
Amplify Flutter Version
1.6.0
Deployment Method
Amplify CLI
Schema
No response
The text was updated successfully, but these errors were encountered: