-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[Bug]: iOS 18 Simulator Problem #3264
Comments
Hello, can you explain further on what the issue is? "the result is unexpected" doesn't tell much. |
Sorry for the unclearity. As you can see from the screenshot after I press save to files, action sheet opens all empty and mostly I cannot close it without restarting the application. All action sheet is unresponsive even the Browse button. When I press hot restart on VSCode application restarts on the background and action sheet stays open like screenshot. This error can cause because of some iOS 18 simulator bug but I wanted to be sure. |
Looking at the logs, the file I am not sure if there has been a change in how the Simulator can access files in iOS 18. In general, the plugin does not manage file access, it takes a file URI provided by the developer and passes it to the platform share method. My recommendation for you is to investigate further why the file is not accessible, if there has been any changes in iOS 18, and as well to test on a physical device too. As well, you can also ask on Stack Overflow. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days |
Platform
iOS 18
Plugin
share_plus
Version
10.0.0
Flutter SDK
3.24.3
Steps to reproduce
I updated my simulator to iOS 18 and now I have very weird problems with simulator.
I have an open issue (flutter/flutter#155535) about flutter but I noticed this now.
When I use shareXFiles to share my file, the result is unexpected.
Code Sample
Logs
Flutter Doctor
Checklist before submitting a bug
flutter pub upgrade
flutter clean
The text was updated successfully, but these errors were encountered: