Mail address to bad format error

SignInWithEmailAndPassword unable to handle error when the email address is badly formatted #3303

Here is my email sign in method in my FirebaseAuthService class:

And here is where the exception should be handled:

And yet when I enter a badly formatted address the process is interrupted at message_codecs.dart file at the method dynamic decodeEnvelope(ByteData envelope) line 572 with error message See screenshot:

I couldn’t figure out how to handle this exception, knowing that it never happened to me before upgrading to firebase_auth: ^0.18.0+1 .

The text was updated successfully, but these errors were encountered:

You need to catch the FirebaseAuthException :

@Ehesp Didn’t work.
Apparently the exception is not rethrown, it is thrown inside the auth module that’s why I cannot handle it.
Here is the function that is throwing it:

Which, then, redirects here:

Can you create a reproduction repository please? I can’t replicate this.

Also, what platform is this?

Do yo mean the CustomErrorPlatformException ?
It is just a custom AlertDialog widget.

Do yo mean the CustomErrorPlatformException ?
It is just a custom AlertDialog widget.

@Ehesp probably referring to my post.
@mehdiRezzagHebla try this on your code:

Do yo mean the CustomErrorPlatformException ?
It is just a custom AlertDialog widget.

@Ehesp probably referring to my post.
@mehdiRezzagHebla try this on your code:

@dhanniex82 Already been suggested by @Ehesp , doesn’t work.
Like I said, it is not a FirebaseAuthException it’s a normal PlatformException that is thrown from message_codecs.dart file in the path C:Program Files [flutter installation folder name] packagesflutterlibsrcservices

the suggested code from @Ehesp on other post got

I managed to get it to work on Web platform though.

Hi @mehdiRezzagHebla,
As requested here, please provide a minimal reproducible code sample that shows the issue.
Thanks.

Hi @mehdiRezzagHebla,
As requested here, please provide a minimal reproducible code sample that shows the issue.
Thanks.

Sorry for the delay, I built a reproducible code but strangely it worked normally, I still fail to identify the difference between the original codebase and copy.
Anyway, I apologize for wasting your time guys, should I delete this issue?

@mehdiRezzagHebla Could you paste your reproducible code? I was getting the same issue as you before, where the message_codecs.dart file was being called when catching exceptions thrown by FirebaseAuth. It’s probably something I’m doing wrong.

Thanks @mehdiRezzagHebla for confirming. Closing this as non-issue.

@dshundal94 I would love to check out your auth_service class maybe it’ll help up see what is wrong.

@mehdiRezzagHebla Here is the link to the test repository: https://github.com/dshundal94/testFlutterFireAuth
I get the unhandled exception when trying to login or even when the FirebaseAuthExceptions pop up.

I know I can probably not explicitly call setState() when trying to update the errorString probably with changeNotifier, but nonentheless, I get messages_codec.dart file getting accessed when trying to login. Most likely, I’m not handling the errors in the proper way.

@dshundal94 your code seems to be fine which makes me less comfortable since I don’t know why this is happening and it could happen any time for some reason I still cannot figure out, I mean imagine this happening in a production ready app.
Please keep me updated if you find anything, I will do the same from my end.

@mehdiRezzagHebla Yeah, I’ve been tackling it for the past few days. I’ve just been trying to write out everything explicitly and see where I went wrong. Just a little frustrating since there seems to be hardly anything documented on why this would happen. I will update here if I find anything related to this.

@mehdiRezzagHebla I updated my repository. Before I was getting some sort of [ERROR:flutter/lib/ui/ui_dart_state(166).cc] Unhandled Exception error in my debug console, now at least I’m not getting that. Although when I run the app in debug mode, it is still accessing message_codecs.dart and throwing a PlatformException.

I changed two things mainly:

1. In my auth.dart file, I’m not error handling on my signIn function there.
2. I changed my signIn function from Future(String) to Future(void) and doing the error handling here with try and catch method.

I don’t know if that helps, but I will continue to work at and update here if I find anything that will help.

@mehdiRezzagHebla I think it might be a problem with how I set up my IDE. After unchecking the BREAKPOINTS: Uncaught Exceptions box, the debugger does not break at the message_codecs.dart file. My suspicion is that the code executes before the catch clause can capture the FirebaseAuthException, but after stepping through the debugger, the catch clause will execute the code written in it without writing an error to the debug console. This seems to be a bug with dart debugging though, because we do catch the exception in our code, yet we still reach a breakpoint when debugging.

Would you know where to follow up on this?

I am using vscode and experiencing the same problem with @dshundal94. Similarly, I was able to solve it by unchecking the ‘Uncaught Exceptions’ checkbox. Afterwards, it runs fine and the FirebaseAuthException was caught. So not sure if the problem is coming from vscode debugger or the firebase auth plugin.

@dshundal94 sorry for the delayed response (timezone difference).
Thank you for spending the effort on tackling this, it seems intriguing, I think it is plausible that the IDE’s debugger config is what’s behind the problem, I am currently debugging an unrelated one in my project, and though I currently have no idea on how to follow up on this, I will get back to it in a few hours and keep you posted with my findings, cheers.

@dshundal94 just a side note on the latest dart v3.14.0 release does this have to anything to do with our issue?

#2699: When using “Debug my code” and an exception occurs with a call stack containing no user code, the top frame will now be selected to make it obvious that execution has paused.

@mehdiRezzagHebla Thanks for looking at this! I think it has to do when handling Futures. Looks like its native to how Dart looks at the debug stack trace as explained in this issue. I guess the current solution would either just step through the code when in debug mode, or uncheck the unhandled exception checkpoint (although this means that it won’t catch the actual unhandled exceptions).

I think you can vote on this open issue here. Again, thanks for looking into this, appreciate the assist!!

@dshundal94 I was lurking around and I fould this description of PlatformException :
Creates a PlatformException with the specified error code and optional message, and with the optional error details which must be a valid value for the MethodCodec involved in the interaction.
I am not sure but I think that it could have something to do with the formatting of PlatformException thrown by the Firebase_Firestore package, I mean a normal PlatformException would be like:

But when you look at the PlatformException not being handled, it does not respect this syntax, take a look at the screenshot you shared above.
@darshankawar @Ehesp any thoughts on this?

@mehdiRezzagHebla Yeah, I saw that too and in my updated repository I don’t get the [ERROR:flutter/lib/ui/ui_dart_state(166).cc] Unhandled Exception: Password associated with this password is wrong message in my debug console. I no longer throw PlatformExceptions when error handling.

I still however, do get the original PlatformException being thrown by the dart language:

In the flutterfire lib, a FirebaseAuthException is thrown anytime a error occurs when trying to sign in with email and password. Here is a link in the flutterfirelib that convert PlatformException to FirebaseAuthException.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

Invalid Email Address Error Codes

If you send bulk emails, you may face the problem of delivery errors. Knowing the reasons will help you cope with it and increase conversions. After registering with SendPulse, you’re welcome to monitor your campaign statistics, including the errors. Keep on reading this article to discover the causes and ways to avoid errors.

Contents

SMTP Error 501

501 Not Implemented

HTTP Error 501 Not implemented

The server either does not recognize the request method, or it cannot fulfill the request.

The command is correct and recognized, but the parameters were invalid. You may receive this error when sending an email to invalid email addresses or an invalid domain name. Also, it may be caused by drops in communication and problems with antivirus settings.

SMTP Error 510

Bad Email Address

Sender’s mail server generates this code. It means that email does not exist or was misspelled. Check your recipients’ emails and correct the typos.

SMTP Error 513

SMTP error 501 5.1.3 Invalid address

SMTP error 501 5.1.3 Bad recipient address syntax

The address type is incorrect, and there may be typos. You may have copied or pasted an address from a website incorrectly. If you have checked all the addresses, and still receive this error, the server needs authentication.

SMTP Error 515

Destination mailbox address invalid

The email address you want to send to may not exist, or there may be typos. Check all the emails for any misspellings.

SMTP Error 530

530 Authentication is required

SMTP Error 530: The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.

You can receive this error due to several reasons:

• You may have an invalid recipient’s address, misspelled the address, or it simply does not exist.
• A recipient’s server could have blacklisted yours only.
• Invalid authentication. Configure the settings.

SMTP Error 553

553 Your email address is denied.

553 sorry, this recipient doesn’t exist.

553 #5.1.8 Domain of a sender’s address does not exist

553 5.3.0 . address does not exist

553 message blocked, you are not authorized to send mail, authentication is required.

You can receive this error if the email address you send to does not exist, or there may be typos, so check. Or, you try to send email using an SMTP of an ISP with no authentication and no connection to the internet via this ISP’s service.

Why do your mailing lists contain invalid email addresses?

Invalid email addresses on your list may be spam traps.

Spam traps are the email addresses used to catch spam senders. They are usually created by inbox or blacklist providers to maintain the anti-spam policy and healthy mailing lists. If you send emails to spam traps, you risk being blacklisted, since it means that you aren’t practicing good mailing list hygiene. Thus, you can get a spam sender reputation.

How can spam traps occur in your mailing list?

Recycled email addresses

These are real but abandoned email addresses. Internet services deactivate addresses after some period of being inactive. Sometimes, they use them as spam traps to identify spammers.

Pristine email addresses

People never use these emails. They are placed on public websites but hidden in the code. They aim to reveal corrupt practices of email list growing, such as website scraping.

Old and inactive subscribers

Your mailing list may include the same email addresses that you’ve collected at the beginning of your business. That’s why some of them can be unengaged. Sending emails to inactive subscribers means that your emails will bounce.

Misspelled email addresses

People can give you an address with the typos deliberately or unintentionally. In the first case, they may have filled out a form that needed an email but didn’t want to share it. Thus they type anything that comes to their mind. Indeed, such an address will be fake. In the second case, it’s just a misprint. Still, you have to take steps to avoid spam traps.

How to avoid sending emails to spam traps?

Contact inactive subscribers

Send an email to subscribers who have not been active for one year, for example. Just ask if they are still interested in your emails. If not – give them a chance to unsubscribe.

Make use of double opt-in

Double-opt in is an excellent practice for building an email list of interested and engaged subscribers. Using this method, users can express their wish to subscribe via the confirmation email. Thus, you will have fewer subscribers, but the mailing list quality is more important.

Check new email addresses

Use a validation tool to find fake and misspelled email addresses.

Never buy mailing lists

The most obvious advice ever, but it works. A purchased email list is a collection of things that looks like a real email address. Surely, they will never bring you engagement.

Besides, when you add a mailing list to SendPulse, you’ll have to prove that you have permission to email the users. This is how an email service prevents sending spam.

Monitor Campaign Statistics

After sending an email campaign with SendPulse, go to «Reports» and check its performance.

In «Error statistics,» you’ll discover the number and type of email delivery errors. They’ll help to:

• clean your mailing list
• keep your sender reputation high
• send campaigns to engaged subscribers only
• pay an email service for active subscribers

If your mailing list has fewer than 500 active subscribers, enjoy the benefits of our free pricing plan!

Send 15,000 emails every month at no cost. Make use of personalization, segmentation, ready-made email templates, and subscription forms to make email marketing yield additional income.

Источник

Comments

  @override
  Future<UserCustom> signInWithEmail(
      String emailAddress, String password) async {
    try {
      UserCredential _signInWithEmailAndPasswordGoogle = await _auth
          .signInWithEmailAndPassword(email: emailAddress, password: password);
      if (_signInWithEmailAndPasswordGoogle.user != null) {
        return _userToUserModel(_signInWithEmailAndPasswordGoogle.user);
      } else {
        throw PlatformException(
            code: 'SIGN_IN_INTERRUPTED', message: 'Sin in interrupted');
      }
    } on PlatformException {
      print('Happened');
      rethrow;
    } catch(e){
      print(e.toString());
    }
  }

  // creating the submit function
  Future<void> _submit(EmailSignInModelProviderPattern model) async {
    // if it is on sign in use sign in function ELSE use register function
    try {
      await model.submit();
      Navigator.pop(context);
    } on PlatformException catch (e) {
      CustomErrorPlatformException(
        title: 'Sign in failed',
        exception: e,
      ).show(context);
    } catch(e){
      print(e.toString());
    }
  }

Exception has occurred.
PlatformException (PlatformException(firebase_auth, com.google.firebase.auth.FirebaseAuthInvalidCredentialsException: The email address is badly formatted., {code: invalid-email, additionalData: {}, message: The email address is badly formatted.}))

try {
  await FirebaseAuth.instance.signInWithEmailAndPassword(
    email: "some invlaid emaill",
    password: "SuperSecretPassword!"
  );
} on FirebaseAuthException catch  (e) {
  if (e.code == 'invalid-email') {
    // Do something :D
  }
}

@override
  dynamic decodeEnvelope(ByteData envelope) {
    // First byte is zero in success case, and non-zero otherwise.
    if (envelope.lengthInBytes == 0)
      throw const FormatException('Expected envelope, got nothing');
    final ReadBuffer buffer = ReadBuffer(envelope);
    if (buffer.getUint8() == 0)
      return messageCodec.readValue(buffer);
    final dynamic errorCode = messageCodec.readValue(buffer);
    final dynamic errorMessage = messageCodec.readValue(buffer);
    final dynamic errorDetails = messageCodec.readValue(buffer);
    if (errorCode is String && (errorMessage == null || errorMessage is String) && !buffer.hasRemaining)
      throw PlatformException(code: errorCode, message: errorMessage as String, details: errorDetails);
    else
      throw const FormatException('Invalid envelope');
  }
}

Future<Map<K, V>> invokeMapMethod<K, V>(String method, [ dynamic arguments ]) async {
    final Map<dynamic, dynamic> result = await invokeMethod<Map<dynamic, dynamic>>(method, arguments);
    return result?.cast<K, V>();
  }

try {
  await FirebaseAuth.instance.signInWithEmailAndPassword(
    email: "some invlaid emaill",
    password: "SuperSecretPassword!"
  ).then((UserCredential user) {
    if( user != null) {
    // do your thing here
}
});
} on FirebaseAuthException catch  (e) {
  print(e.code);
  print(e.message);
 // do some other thing
  }
}

.then method
and I need to add user null check after that.

PlatformException(
title: 'Some Title Here',
content: 'Description here',
message: 'Some message here')