-
Notifications
You must be signed in to change notification settings - Fork 32
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
Replace file_selector with file_picker in all of our dependencies #886
Comments
@sachins-geekyants @Sardar1208 if you need an example: https://github.com/atsign-foundation/noports/tree/xc-npt-desktop-mvp |
Found the root cause of the issue to be the file_selector package, I am repurposing this ticket to replace file_selector with file_picker, as it is better maintained. When we first started using file_picker, it didn't have desktop support so we continued to use file_selector. But now file_picker seems to be the simpler option. |
I know that both at_onboarding_flutter and at_backupkey_flutter use file_selector, there may be other packages which I am not aware of. |
Our packages that uses file_selector:
|
Which at_widget package you find issue with?
at_onboarding_flutter
On what platforms did you experience the issue?
MacOS
What version are you using?
at_onboarding_flutter : trunk
Flutter 3.24.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 80c2e84975 (9 days ago) • 2024-07-30 23:06:49 +0700
Engine • revision b8800d88be
Tools • Dart 3.5.0 • DevTools 2.37.2
What happened?
Onboarding widget is crashing with errors.
Steps to reproduce
1. Follow this guide - https://docs.atsign.com/tutorials/flutter-and-atsdk-app 2. Do step 2 from here - https://pub.dev/packages/at_onboarding_flutter 3. Pin at_onboarding_flutter to trunk of this repo 4. Try to run the app 5. Press "onboard an atsign" 6. Error occurs
Additional info
Note that prior to trying the trunk code, I tried 6.1.7 and it also hung:
Press "onboard an atsign" > press "already have an atsign" > press "upload atkeys" then it hangs forever.
Relevant log output
The text was updated successfully, but these errors were encountered: