Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Conversation

ffeu
Copy link
Contributor

@ffeu ffeu commented Sep 20, 2018

intends to fix flutter/flutter#17699 and fix flutter/flutter#20378

Removing local cache of getToken() in the dart part of the plugin. Now getToken() calls directly its counterparts in the iOS and Android implementations. This enables obtaining its value without calling configure() or having to wait for a new token refresh.

@ffeu
Copy link
Contributor Author

ffeu commented Sep 20, 2018

@kroikie let me know if there's any improvement, tested on real devices on iOS and Android

mehmetf and others added 4 commits September 24, 2018 17:15
@ffeu
Copy link
Contributor Author

ffeu commented Sep 27, 2018

@kroikie BTW, there's this one too. it closes two issues! 😀

@calebisstupid
Copy link

This PR fixes the hanging getToken() call for me in simulator as well.

kroikie and others added 4 commits October 12, 2018 13:59
)

* Bump firebase_remote_config Android dependencies to latest.

* Bump pubspec version
* Bump firebase_ml_fision Android dependencies to latest

* bump pubspec version
Add clearMarkers() functionality to GoogleMapController. This method will clear all markers currently present on the map.
@beardo01
Copy link

Can also confirm that this has fixed the getToken() hanging issue for me. Another respectful ping to @kroikie to accept this.

pdefuns and others added 2 commits October 15, 2018 08:48
Now the users can determine two things:
- Whether the phone is capable of biometrics.
- Whether any biometric checks are available to the app.
@muirandy
Copy link

I'm new to Flutter and am evaluating it for use with Firebase. This plugin is obviously important!
I've been through a tutorial, and it behaves inconsistently - I believe this PR is the fix.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@ffeu
Copy link
Contributor Author

ffeu commented Oct 16, 2018

yeah, i messed up this branch/PR. :(

sorry about that, I'll have to recreate it in another PR.

@beardo01
Copy link

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

4 similar comments
@beardo01
Copy link

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@beardo01
Copy link

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@beardo01
Copy link

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@beardo01
Copy link

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@Hixie
Copy link
Contributor

Hixie commented Oct 24, 2018

@ffeu Are you planning on submitting a new PR as per your comment above?

@ffeu
Copy link
Contributor Author

ffeu commented Oct 24, 2018

@Hixie yes, give me just a few minutes

@ffeu
Copy link
Contributor Author

ffeu commented Oct 24, 2018

replaced by #869

@ffeu ffeu closed this Oct 24, 2018
@ffeu ffeu deleted the gettoken_platform branch November 16, 2018 13:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet