[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.

Comienza con packages/firebase-messaging-core/index.android.ts en las líneas 314-319 y sigue la ruta de Android 33 de requestPermission usando la llamada de ejemplo del issue. Compara su comportamiento de rechazo con la implementación de iOS descrita por el reportero. Se considera terminado cuando se entiende el comportamiento en el emulador o dispositivo y el resultado de permiso denegado es coherente con la expectativa multiplataforma indicada.