You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Android, the email client opens, and I can wait as long as I want to send or cancel. Then when it returns to the app, the future completes and my code continues. On iOS, the app continues without waiting for the client to complete. It also does not open in a way that pauses the app lifecycle, so I can't even use resume to carry on. Is there anyway to wait for the client to complete and return to the app on iOS?
Using 5.0.0, updated to 5.0.2 and still have the same issue.
The text was updated successfully, but these errors were encountered:
@mbarmettler@SRadfordM
I've made a pull request that enhances the functionality of the flutter_email_sender package by enabling event triggers when users perform email actions like sending, canceling, or saving. These updates aim to provide more comprehensive status updates, significantly improving the package's overall capabilities.
Additionally, I've integrated this upgraded version of the flutter_email_sender package into our project using the specific commit 24d942f. This version is particularly beneficial during the development phase, allowing us to leverage the latest changes and thoroughly test the enriched functionality it offers.
Feel free to incorporate this updated package by including the following configuration in your pubspec.yaml file:
On Android, the email client opens, and I can wait as long as I want to send or cancel. Then when it returns to the app, the future completes and my code continues. On iOS, the app continues without waiting for the client to complete. It also does not open in a way that pauses the app lifecycle, so I can't even use resume to carry on. Is there anyway to wait for the client to complete and return to the app on iOS?
Using 5.0.0, updated to 5.0.2 and still have the same issue.
The text was updated successfully, but these errors were encountered: