Skip to content
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

Extracting UI responsibility, named parameters, android dismissal fix #189

Merged
merged 1 commit into from
Aug 24, 2024

Conversation

mikaelwills
Copy link
Collaborator

Three main fixes:

Android calling UI wasn't being dismissed when answerIncomingCall() was being called from in app UI.
needed to call setCurrent() in native android.

I spent ages trying to figure out why things weren't working only to realise i was passing the caller name into the handle parameter. Added named parameters to all functions so that shouldnt happen for anyone in the future and things are clearer.

In recent versions of flutter the framekwork suggest against passing BuildContexts across async gaps also your app should be responsible for how it looks not an external package. For the default permissions UI i've extracted out the responsibility so the app using the package can determine how that dialog looks.

Also some updates to the readme!

Copy link
Member

@cloudwebrtc cloudwebrtc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@cloudwebrtc cloudwebrtc merged commit 0377bfd into flutter-webrtc:master Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants