Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications.scheduleNotificationAsync when called 2nd time resulted in undefined is not a function at getRandomBase64 #927

Open
krishn1232427 opened this issue Jul 30, 2023 · 2 comments

Comments

@krishn1232427
Copy link

Describe the bug
Notifications.scheduleNotificationAsync when called 2nd time resulted in undefined is not a function at getRandomBase64

To Reproduce
Steps to reproduce the behavior:
const notificationContent1 = {
title: 'Notification 1',
body: 'This is notification 1.',
identifier: 'notification_1',
};

const notificationReq1 = await Notifications.scheduleNotificationAsync({
  content: notificationContent1,
  trigger: {
    seconds: 30,
  },
});
console.log(
  "notificationReq1:",
  notificationReq1
);
const notificationContent2 = {
  title: 'Notification 2',
  body: 'This is notification 2.',
  identifier: 'notification_2',
};

const notificationReq2 = await Notifications.scheduleNotificationAsync({
  content: notificationContent2,
  trigger: {
    seconds: 60,
  },
});
console.log(
  "notificationReq2:",
  notificationReq2
);

Expected behavior
A news Notification has to be set.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Android

Smartphone (please complete the following information):
Android

Additional context
Add any other context about the problem here.

@yasin459
Copy link

having same issue, scheduleNotificationAsync works fine on first call but returns TypeError: undefined is not a function on second call.

@danil-davydenko
Copy link

having same issue, scheduleNotificationAsync works fine on first call but returns TypeError: undefined is not a function on second call.

any fixes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants