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

packages/firebase-messaging-core/index.android.ts の314-319行目から始め、Issueのサンプル呼び出しを使って Android 33 の requestPermission パスを追跡してください。拒否時の動作を、報告者が説明している iOS 実装と比較してください。エミュレーターまたはデバイスでの動作を理解し、拒否された権限の結果が示されたクロスプラットフォームの期待と一致すれば完了です。