-
Notifications
You must be signed in to change notification settings - Fork 17
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
Library seems not worked #31
Comments
What version of React Native, react-native-push-notification, react-native-simple-alarm, @react-native-community/async-storage @react-native-community/push-notification-ios are you using? |
Here is the information:
|
I am also having exact same issues, @liplylie |
@liplylie Thanks. In file activateAlarm.js :
|
@ameya-linge hmm, this was working in the past, I'll take a look into this |
@ameya-linge yep, you're right, repeating push notifications in specific intervals isn't supported in iOS. Will need to think of a workaround for this |
@hcphuc2595 I'll take at the android error |
@liplylie can we implement the library with native code for alarms? Because I think react-native-push-notifications has some issues with android. It does not trigger. |
Hello,
I tried to implement this library into my project for sending scheduled alerts. but I found out some problems.
On IOS: The alert is sent every minute (not at the date and snooze expected).
On Android: I see in the log that alert is created but I received nothing (no alerts, no push notifications). I tried to replicate the same configurations as in example app but still not work.
const dateForAlert = moment() .add(3, 'minutes') .startOf('minute') .format(); const resAlarm = await createAlarm({ active: true, date: dateForAlert, allowWhileIdle: true, message:
${loadID} ${I18n.t('alarmMessage')}, // snooze: SNOOZE_MINUTES, snooze: 2, userInfo: { tripID, loadID, }, });
Moreover on Android, I always have the error in debug mode and in release apk mode, the app crashed. Here is the error I can find in the log.
Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:592:3) at tryReadSync (fs.js:366:20) at Object.readFileSync (fs.js:403:19) at UnableToResolveError.buildCodeFrameMessage (/home/brady/obs-websocket-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:347:17) at new UnableToResolveError (/home/brady/obs-websocket-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (/home/brady/obs-websocket-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (/home/brady/obs-websocket-app/node_modules/metro/src/node-haste/DependencyGraph.js:413:43) at /home/brady/obs-websocket-app/node_modules/metro/src/lib/transformHelpers.js:317:42 at /home/brady/obs-websocket-app/node_modules/metro/src/Server.js:1471:14 at Generator.next (<anonymous>)
The text was updated successfully, but these errors were encountered: