-
I'm not sure this is issue of flutterfire, or dart... anyway, below code's catch statement not worked at all: try {
return await FirebaseAuth.instance
.signInWithEmailAndPassword(email: email, password: password); // if exception occurred, it became 'unhandled exception'
} on FirebaseAuthException catch (e, s) {
// not came here :(
} catch (e, s){
}
} only below code works properly: try {
return await FirebaseAuth.instance
.signInWithEmailAndPassword(email: email, password: password);
} on FirebaseAuthException catch (e) {
// came here :) but why?
} catch (e, s){
}
} I thought if there is no stacktrace (2nd parameter) it should be null or at least go to catch statement, but it just thrown to upper method. Is this normal behavior? It so, should I check every libraries that I used whether they need catch block with one or two parameters? |
Beta Was this translation helpful? Give feedback.
Answered by
roeniss
Mar 7, 2021
Replies: 1 comment
-
After rebuild, those problem was gone, maybe I messed up something for a moment... |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
roeniss
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After rebuild, those problem was gone, maybe I messed up something for a moment...