[messaging-core] Problems with requesting permissions on Android 33

I'm trying to migrate from the old firebase plugin to this one, and I'm getting some strange problem testing on a simulator with API 33. As soon as I call the request permissions, I do not get any prompts and I get a rejection. Here is a sample code:

export async function onTap() {
  try {
    const result = await MessagingCore.getInstance().requestPermission();
    console.log("RES", result);
  }
  catch (e) {
    console.error("ERROR", e);
  }
}

From what I see it is because of this:
https://github.com/NativeScript/firebase/blob/889726640381cb4a0cdbe855f658ff3245a0eb3d/packages/firebase-messaging-core/index.android.ts#L314-L319

Does requesting permissions for notifications work only on physical devices?

Also why does this code reject while the iOS code resolves even if permission is denied but with the correct status code? Shouldn't this be changed to resolve(AuthorizationStatus.DENIED) for better cross platform interoperability? Right now I have to surround the request call with an empty try/catch to simulate similar behavior as on iOS.

Inizia da packages/firebase-messaging-core/index.android.ts alle righe 314-319 e traccia il percorso requestPermission di Android 33 usando la chiamata di esempio nell’issue. Confronta il comportamento in caso di rifiuto con l’implementazione iOS descritta dal segnalatore. Il lavoro è completato quando il comportamento sull’emulatore o sul dispositivo è compreso e il risultato della permission negata è coerente con l’aspettativa multipiattaforma indicata.