SMS sending problems with secondary factor authentication

[Karman40]

trafficstars

Version info

Angular CLI: 14.2.13
Node: 20.9.0 (Unsupported)
Package Manager: npm 10.1.0 
OS: win32 x64

Angular: 14.3.0
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1402.13
@angular-devkit/build-angular      14.2.13
@angular-devkit/core               14.2.13
@angular-devkit/schematics         14.2.13
@angular/cdk                       14.2.7
@angular/cli                       14.2.13
@angular/fire                      7.6.1
@angular/material                  14.2.7
@angular/material-moment-adapter   14.2.7
@schematics/angular                14.2.13
rxjs                               7.8.1
typescript                         4.8.4
firebase                           9.23.0

The problem

I use multi-factor authentication. Email and password confirmation with a one-time SMS code. The SMS is 98% not sent and sometimes (I can't find a system) it is sent and received. Neither the console nor does it write any errors, it's sending SMS successfully.

Code

The source code: https://gitlab.hostpark.hu/-/snippets/1

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[Karman40]

the administration panel shows the given SMS as sent. Which sometimes arrives, sometimes doesn't.

[Sapython]

Have you tried this multiple Cell service providers in you area. Because if the console is saying the message is sent, then the console backend (GCP) must have sent it. But if it is not received on your end it might be an issue that your cell provider is blocking that message.

More steps for debugging

1. Try with different cell/mobile numbers from different providers (ask a friend or a family member for it)
2. Try to do it without multifactor and see if the issue remains same or does the result changes. (if it does than firebase has to do something with this. And a better help will be provided over https://github.com/firebase/firebase-js-sdk/issues , because this doesn't look like an issue with angular fire library but rather with firebase)