APNS token has not been set yet. Please ensure the APNS token is available by calling `getAPNSToken()`.

[spyingcoder]

flutterfire/packages/firebase_messaging/firebase_messaging_platform_interface/lib/src/method_channel/method_channel_messaging.dart

Line 137 in 4e7f800

if (token == null) {

This doesn't make any sense here. Internally in this package, we are calling getAPNSToken(). but for that value(if nulls), then we are throwing this exceptions "APNS token has not been set yet. Please ensure the APNS token is available by calling getAPNSToken()." even though we are already calling this function.

[SelaseKay]

Hi @spyingcoder, I'm not really sure I understand what you mean. My guess is your issue is probably related to #17749. Closing as duplicate.

[spyingcoder]

Hey @SelaseKay , please don't close this issue without understanding the whole picture as you already quoted "I'm not really sure". You closed an issue based on a probability. This is not the right way I guess.

My point is not about APNS token availability. It’s about the error message itself being misleading. The code calls getAPNSToken() internally, and if it’s null, the exception tells developers to call getAPNSToken(), which they already did by using the API. The message should instead explain why the token may be null and what to do next (permissions, retry, etc.).

Or maybe, you can check(if possible) whether the Firebase has been misconfigured by the developer. Been there a couple of times.

[spyingcoder]

Also, in the attached link you have redirected me to this thread itself (#17749).

[SelaseKay]

Hi @spyingcoder, apologies. I meant to redirect you to this issue: #17729. I'll look into this.

[SelaseKay]

Hi @spyingcoder, your issue is indeed valid. My apologies for closing it earlier due to a misunderstanding. I’ll be creating a PR to update the error message. Sorry for any inconvenience this may have caused.

[spyingcoder]

@SelaseKay Thanks for your understanding on this. I've already reviewed the #17729, but found that their issue is limited to simulators only. I've had this issue on the real device as well as on TestFlight.