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
failed in processing atkey zip file Error in the onboarding widget version 2.0.0 #65
Comments
Please stop mentioning me in this repo. Thank you |
Hi @Intiserahmed I'm going to send you a video showing you how to put a space separator between @ and buzz. |
@ksanty Please stop mentioning my username in this repository. Thank you very much |
Same issue when trying
It appears to start at
Removing the typecast and changing result's type to FilePickerResult? allows the project to build, however I'm still unable to onboard. I get sent back to the upload screen. |
Both ".zip" and ".atKeys" extension files seem to be working fine with at_onboarding_flutter v2.1.0 |
@sarika01 checked giving the future file picker error as @XavierChanth mentioned. |
Could it be from the flutter sdk version I'm using? #/example/pubspec.yaml
environment:
sdk: ">=2.7.0 <3.0.0" I suppose that my issues come from using sdk 2.12 in pubspec.yaml: #/my_app/pubspec.yaml
environment:
sdk: ">=2.12.0 <3.0.0" |
@XavierChanth 2.12 is for null safety... I'm afraid 2.7 doesn't support null safety. |
I'm using 2.12, example is using 2.7, I get major issues when trying to use 2.7, since all the code is written to use null safety in the app. |
@Intiserahmed does the issue exist with at_onboarding_flutter v2.1.0? |
@murali-shris Yeap It's working like a charm |
Closing this on your behalf @Intiserahmed |
Describe the bug
When I try to pick my atkey zip file from my android phone it gives me the error in the wavi app. I also faced the same error when I used onboarding widget 2.0.0 in demo apps
To Reproduce
Steps to reproduce the behavior:
First I '...'
Then I '...'
And then '...'
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Smartphone (please complete the following information):
Were you using an @Application when the bug was found?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: