Encountering a snag when trying to grant notification permission in the Expo app

Question

Encountering a snag when trying to grant notification permission in the Expo app

I am experiencing an issue with a simple code that previously asked for notification permissions. However, I am now encountering the following error:

"Error: Encountered an exception while calling native method: Exception occurred while executing exported method requestPermissionsAsync on module ExpoNotificationPermissionsModule: String resource ID #0xffffffff"

Here is the code in question:

    if (isDevice) {
        const { status: existingStatus } = await Notifications.getPermissionsAsync();
        let finalStatus = existingStatus;
        if (existingStatus !== "granted") {
            const { status } = await Notifications.requestPermissionsAsync();
            finalStatus = status;
        }
        if (finalStatus !== "granted") {
            Alert.alert("Falha ao obter permissão para notificações push!", "É necessário permitir o envio de notificações push para o aplicativo funcionar corretamente.");
            return "";
        }
        token = (await Notifications.getExpoPushTokenAsync()).data;
    } else {
        alert("Para gerar o token de notificação você precisa estar em um dispositivo físico!");
    }

javascript android typescript expo

Answer 1

Answer №1

When using Android 13, application users are now required to actively choose to receive notifications by responding to a permissions prompt that is automatically generated by the operating system. This prompt will only show up once at least one notification channel has been established. It is crucial to call setNotificationChannelAsync before attempting to obtain a push token with getDevicePushTokenAsync or getExpoPushTokenAsync. For more details on the updated notification permission process for Android 13, refer to the official documentation.

async function registerForPushNotificationsAsync() {
  let token;

  if (Platform.OS === 'android') {
    await Notifications.setNotificationChannelAsync('default', {
      name: 'default',
      importance: Notifications.AndroidImportance.MAX,
      vibrationPattern: [0, 250, 250, 250],
      lightColor: '#FF231F7C',
    });
  }

  if (Device.isDevice) {
    const { status: existingStatus } = await Notifications.getPermissionsAsync();
    let finalStatus = existingStatus;
    if (existingStatus !== 'granted') {
      const { status } = await Notifications.requestPermissionsAsync();
      finalStatus = status;
    }
    if (finalStatus !== 'granted') {
      alert('Failed to get push token for push notification!');
      return;
    }
    token = (await Notifications.getExpoPushTokenAsync()).data;
    console.log(token);
  } else {
    alert('Must use physical device for Push Notifications');
  }

  return token;
}

To resolve any issues related to permission prompts, it is recommended to clear storage data and uninstall the Expo Go app. Reinstalling the app should trigger the permission prompt accordingly.

Answer 2

When using Android 13, application users are now required to actively choose to receive notifications by responding to a permissions prompt that is automatically generated by the operating system. This prompt will only show up once at least one notification channel has been established. It is crucial to call setNotificationChannelAsync before attempting to obtain a push token with getDevicePushTokenAsync or getExpoPushTokenAsync. For more details on the updated notification permission process for Android 13, refer to the official documentation.

async function registerForPushNotificationsAsync() {
  let token;

  if (Platform.OS === 'android') {
    await Notifications.setNotificationChannelAsync('default', {
      name: 'default',
      importance: Notifications.AndroidImportance.MAX,
      vibrationPattern: [0, 250, 250, 250],
      lightColor: '#FF231F7C',
    });
  }

  if (Device.isDevice) {
    const { status: existingStatus } = await Notifications.getPermissionsAsync();
    let finalStatus = existingStatus;
    if (existingStatus !== 'granted') {
      const { status } = await Notifications.requestPermissionsAsync();
      finalStatus = status;
    }
    if (finalStatus !== 'granted') {
      alert('Failed to get push token for push notification!');
      return;
    }
    token = (await Notifications.getExpoPushTokenAsync()).data;
    console.log(token);
  } else {
    alert('Must use physical device for Push Notifications');
  }

  return token;
}

To resolve any issues related to permission prompts, it is recommended to clear storage data and uninstall the Expo Go app. Reinstalling the app should trigger the permission prompt accordingly.

Answer 3

Answer №2

Similar situation happened to me as well, where the notification feature was functioning properly until a recent time. Without even delving into the specific section of code responsible for handling notifications, I realized that the issue might not lie within the codebase itself. Upon further investigation, I discovered that my phone had undergone a recent OS update. In response, I took the step of uninstalling Expo and clearing all the associated app data and storage. Additionally, I made sure to update expo-cli and reverted back to the original, untouched version of the codebase on the same device. This led to a prompt for notification permissions and successfully resolved that particular aspect of the code. However, it appears that secure storage is currently facing issues. Regardless, this process may serve as a helpful starting point for troubleshooting on your end.

Answer 4

Similar situation happened to me as well, where the notification feature was functioning properly until a recent time. Without even delving into the specific section of code responsible for handling notifications, I realized that the issue might not lie within the codebase itself. Upon further investigation, I discovered that my phone had undergone a recent OS update. In response, I took the step of uninstalling Expo and clearing all the associated app data and storage. Additionally, I made sure to update expo-cli and reverted back to the original, untouched version of the codebase on the same device. This led to a prompt for notification permissions and successfully resolved that particular aspect of the code. However, it appears that secure storage is currently facing issues. Regardless, this process may serve as a helpful starting point for troubleshooting on your end.

Answer 5

Answer №3

After uninstalling Expo Go and doing a fresh reinstall, everything worked perfectly for me. I also made sure to update the expo-cli by running "npm install -g eas-cli". Hopefully this solution will be helpful for others facing similar issues.

Answer 6

After uninstalling Expo Go and doing a fresh reinstall, everything worked perfectly for me. I also made sure to update the expo-cli by running "npm install -g eas-cli". Hopefully this solution will be helpful for others facing similar issues.

Answer 7

Answer №4

After following Irfan Muhammad's advice, I decided to relocate the registerForPushNotificationsAsync function to the beginning of my App.js file. Then, I uninstalled expo go and installed it again as instructed.

I cannot be certain if moving the function had any impact, but it is the step that I took. Surprisingly, the prompt appeared right away after making these adjustments.

Answer 8

After following Irfan Muhammad's advice, I decided to relocate the registerForPushNotificationsAsync function to the beginning of my App.js file. Then, I uninstalled expo go and installed it again as instructed.

I cannot be certain if moving the function had any impact, but it is the step that I took. Surprisingly, the prompt appeared right away after making these adjustments.

Answer 9

Answer №5

If you're looking to resolve this issue, make sure to check out the following guide: expo notification setup

Include the code below if it's not already present

  if (Platform.OS === 'android') {
    await Notifications.setNotificationChannelAsync('default', {
      name: 'default',
      importance: Notifications.AndroidImportance.MAX,
      vibrationPattern: [0, 250, 250, 250],
      lightColor: '#FF231F7C',
    });
  }

Remember to add the projectId within the getExpoPushTokenAsync function

  token = (
      await Notifications.getExpoPushTokenAsync({
        projectId: Constants.expoConfig.extra.eas.projectId,
      })

Enclose the entire code block in a try-catch statement to catch any potential issues that may arise in the future

Answer 10

If you're looking to resolve this issue, make sure to check out the following guide: expo notification setup

Include the code below if it's not already present

  if (Platform.OS === 'android') {
    await Notifications.setNotificationChannelAsync('default', {
      name: 'default',
      importance: Notifications.AndroidImportance.MAX,
      vibrationPattern: [0, 250, 250, 250],
      lightColor: '#FF231F7C',
    });
  }

Remember to add the projectId within the getExpoPushTokenAsync function

  token = (
      await Notifications.getExpoPushTokenAsync({
        projectId: Constants.expoConfig.extra.eas.projectId,
      })

Enclose the entire code block in a try-catch statement to catch any potential issues that may arise in the future

Answer 11

Answer №6

The advice given by @sreedeep regarding FCM is valuable, suggesting the use of getDevicePushTokenAsync rather than getExpoPushTokenAsync. You can find more details about this recommendation here

Answer 12

The advice given by @sreedeep regarding FCM is valuable, suggesting the use of getDevicePushTokenAsync rather than getExpoPushTokenAsync. You can find more details about this recommendation here

Answer 13

Answer №7

If you're having trouble with the Expo Go app, try clearing its storage and then relaunching the app. This simple fix has worked for me in the past.

Answer 14

If you're having trouble with the Expo Go app, try clearing its storage and then relaunching the app. This simple fix has worked for me in the past.

Encountering a snag when trying to grant notification permission in the Expo app

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Answer №6

Answer №7

Similar questions

Can we limit the return type of arrow function parameters in TypeScript?

Engaging Resources for Introducing Children to Javascript Programming

Assign the JSON string to a variable

Angular backslash is encoded

A step-by-step guide on sending a fetch request to TinyURL

Error: Cannot locate 'import-resolver-typescript/lib' in jsconfig.json file

Failure to Present Outcome on Screen

The Mongoose model is having issues being imported into a different Component

JSON input in react.js sadly ended abruptly

Global Positioning System (GPS) tracking combined with accelerometer

What is the best way to exclude an external HTML file from being displayed on the home page?

Setting the base URL in Next.js according to an environment variable: a step-by-step guide

What steps should I take to ensure that the proper link is loaded and opened when the loop is clicked?

405 error: NGINX blocking POST method in Django DRF Vue.js application

Having trouble with jQuery.cookie saving my JSON data

React Chart.js allows for consistent spacing for x-axes by displaying dates in a well-organized

Picasso encountered a problem when trying to process a list of images

Error: A stream was expected, but instead you provided an object that is invalid. Acceptable options include an Observable, Promise, Array, or Iterable

Error: HTMLAnchorElement.linkAction is attempting to access an undefined property 'add', resulting in an uncaught TypeError

The Axios GET request was not functioning properly after attempting to use Axios stream.on("data")